Triple
T18648102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Fairley |
E455855
|
entity |
| Predicate | helpedLead |
P40241
|
FINISHED |
| Object | Auburn Tigers to BCS National Championship Game victory |
—
|
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: Auburn Tigers to BCS National Championship Game victory | Statement: [Nick Fairley, helpedLead, Auburn Tigers to BCS National Championship Game victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedLead Context triple: [Nick Fairley, helpedLead, Auburn Tigers to BCS National Championship Game victory]
-
A.
helpsLead
chosen
Indicates that one entity assists or contributes to another entity’s act of leading or guiding.
-
B.
leadType
Indicates the specific category or classification of a lead within a lead management or sales context.
-
C.
leadsInto
Indicates that one entity serves as an entry or transition point that directly connects or opens into another entity.
-
D.
leadHijacker
Indicates that one entity is the primary organizer or chief perpetrator among a group of hijackers involved in a hijacking event.
-
E.
leads
Indicates having primary responsibility for directing, guiding, or managing another entity or group toward a goal or outcome.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500f007c81908b1835569be913d7 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.