Triple
T31394926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke vs. North Carolina games |
E800839
|
entity |
| Predicate | firstMeetingYearApprox |
P207418
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Duke vs. North Carolina games, firstMeetingYearApprox, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMeetingYearApprox Context triple: [Duke vs. North Carolina games, firstMeetingYearApprox, early 20th century]
-
A.
firstMeetingYear
Indicates the calendar year in which two entities first met or had their initial encounter.
-
B.
firstEngagementYear
Indicates the calendar year in which an entity first became engaged in a specified relationship, activity, or involvement.
-
C.
yearOfMeeting
Indicates the specific calendar year in which the meeting between the referenced entities took place.
-
D.
firstMeetingAge
Indicates the age at which two entities first met or initially came into contact.
-
E.
firstArrivalYear
Indicates the calendar year in which an entity first arrived at or was initially present in a specified place or context.
- F. None of above. chosen
Provenance (4 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:19 p.m.