Triple
T20267456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Anthony |
E499004
|
entity |
| Predicate | startTime (Chickenfoot membership) |
P66434
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Michael Anthony, startTime (Chickenfoot membership), 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTime (Chickenfoot membership) Context triple: [Michael Anthony, startTime (Chickenfoot membership), 2008]
-
A.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
B.
startTimeNote
Indicates the specific time-related note or annotation associated with when an event or action begins.
-
C.
startTime (Chief Judge SDNY)
Indicates the specific time at which the tenure or role of the Chief Judge of the Southern District of New York begins.
-
D.
positionStartTime
chosen
Indicates the time at which a position, role, or placement begins.
-
E.
startDuring
Indicates that one event or interval begins at some point strictly within the duration of another event or interval, but not at its start.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674d001f081908910eedd262ae13a |
completed | April 20, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:42 p.m.