Triple
T183858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Nicol |
E3936
|
entity |
| Predicate | managerialTenureStart |
P1814
|
FINISHED |
| Object | 2002 with New England Revolution |
—
|
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: 2002 with New England Revolution | Statement: [Steve Nicol, managerialTenureStart, 2002 with New England Revolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managerialTenureStart Context triple: [Steve Nicol, managerialTenureStart, 2002 with New England Revolution]
-
A.
officeHolderStartTime
chosen
Indicates the date and time at which an individual begins holding a particular office or position.
-
B.
managerDebutYear
Indicates the year in which an individual first began their role as a manager.
-
C.
commissionerStartYear
Indicates the calendar year in which an entity began serving in the role of commissioner.
-
D.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
E.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25926be9c8190a4cfce66f57589d1 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566dfc388190988b1b42d5daaafe |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.