Triple
T14629259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franco Harris |
E343435
|
entity |
| Predicate | secondaryTeamTenureEnd |
P115110
|
FINISHED |
| Object | 1984 |
—
|
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: 1984 | Statement: [Franco Harris, secondaryTeamTenureEnd, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryTeamTenureEnd Context triple: [Franco Harris, secondaryTeamTenureEnd, 1984]
-
A.
teamTenure
Indicates the duration or length of time an entity has been part of a particular team.
-
B.
secondTermEnd
Indicates that the referenced time or event marks the conclusion of the second term in a sequence of terms.
-
C.
secondOfficeHolderEndDate
Indicates the date on which the second person holding a particular office or position ended their term.
-
D.
endOfTenure
Indicates the point or event at which an entity’s period of holding a role, position, or office concludes.
-
E.
holderEndDate
Indicates the date on which an entity’s role as holder of something (e.g., an asset, position, or right) comes to an end.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4a7c8fc81909d10c1f563d7d1e7 |
completed | April 14, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:26 a.m.