Triple
T30898815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Find a Way |
E787101
|
entity |
| Predicate | helpedBroaden |
P5633
|
FINISHED |
| Object | Amy Grant mainstream popularity |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Amy Grant mainstream popularity | Statement: [Find a Way, helpedBroaden, Amy Grant mainstream popularity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedBroaden Context triple: [Find a Way, helpedBroaden, Amy Grant mainstream popularity]
-
A.
broaderTarget
Indicates that one target concept encompasses or is more general than another, defining a broader-to-narrower target relationship.
-
B.
helpedDiscover
Indicates that one entity assisted another entity in the process of discovering or uncovering something.
-
C.
expandedBy
chosen
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
D.
laterHelps
Indicates that one entity provides help or assistance to another at a subsequent time rather than immediately.
-
E.
helpsIn
Indicates that one entity provides assistance, support, or aid to another entity in performing or achieving a particular task, activity, or goal.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923d7438819088dfc308d1e22fd0 |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:50 p.m.