Triple
T37069193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Age of Opportunity |
E917528
|
entity |
| Predicate | hasStudyGuide |
P53453
|
FINISHED |
| Object | Age of Opportunity study guide |
—
|
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: Age of Opportunity study guide | Statement: [Age of Opportunity, hasStudyGuide, Age of Opportunity study guide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudyGuide Context triple: [Age of Opportunity, hasStudyGuide, Age of Opportunity study guide]
-
A.
hasDiscussionGuide
Indicates that an entity is associated with or accompanied by a specific discussion guide used to structure or facilitate conversation.
-
B.
hasStudied
Indicates that an entity has engaged in learning or academic work related to another entity (such as a subject, field, or course).
-
C.
isStudiedUsing
Indicates that something serves as the method, tool, or approach by which something else is examined, analyzed, or researched.
-
D.
hasGuides
chosen
Indicates that an entity is associated with one or more guides that provide direction, instruction, or assistance.
-
E.
hasStudyType
Indicates that an entity is associated with or characterized by a particular type or design of study.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
Created at: May 3, 2026, 4:14 p.m.