Triple
T14629258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franco Harris |
E343435
|
entity |
| Predicate | secondaryTeamTenureStart |
P28287
|
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, secondaryTeamTenureStart, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryTeamTenureStart Context triple: [Franco Harris, secondaryTeamTenureStart, 1984]
-
A.
teamTenure
Indicates the duration or length of time an entity has been part of a particular team.
-
B.
homeTeamSince
Indicates the point in time from which a particular team has been designated as the home team for a given context or venue.
-
C.
successorTeamInception
Indicates that one team was formed as the direct successor to another team at the time of its inception.
-
D.
secondTermStartYear
chosen
Indicates the calendar year in which an entity’s second term in a role, office, or position begins.
-
E.
team1Established
Indicates that the first team in a given context has been founded or formally established.
- 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_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. |
Created at: April 10, 2026, 1:26 a.m.