Triple
T20050689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nate Thurmond |
E499188
|
entity |
| Predicate | quadrupleDoubleDate |
P6878
|
FINISHED |
| Object | 1974-10-18 |
—
|
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: 1974-10-18 | Statement: [Nate Thurmond, quadrupleDoubleDate, 1974-10-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quadrupleDoubleDate Context triple: [Nate Thurmond, quadrupleDoubleDate, 1974-10-18]
-
A.
integratedDate
Indicates the date on which one entity was incorporated, combined, or brought into a larger system or whole.
-
B.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
D.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
E.
morePreciseDate
Indicates that one date value specifies a more detailed or exact point in time than another related date value.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632d9d888190b0985bb5ed989311 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.