Triple
T3102542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Art Rooney |
E64752
|
entity |
| Predicate | dateFoundedTeam |
P45941
|
FINISHED |
| Object | 1933-07-08 |
—
|
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: 1933-07-08 | Statement: [Art Rooney, dateFoundedTeam, 1933-07-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateFoundedTeam Context triple: [Art Rooney, dateFoundedTeam, 1933-07-08]
-
A.
team1Established
Indicates that the first team in a given context has been founded or formally established.
-
B.
team2Established
Indicates that a second team (team2) has been formally created or founded at a specific point in time.
-
C.
teamFoundedLegacy
Indicates that a team was established as a continuation, successor, or legacy of a prior organization or team.
-
D.
departmentFormed
Indicates that a specific department has been created or established, often at a particular time or under certain conditions.
-
E.
teamFoundedAs
Indicates the original name or identity under which a team was first established or created.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada26df128819086541db7680c8c24 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df06ed88190809f0683122caa5a |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.