Triple
T222002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Yankees vs Baltimore Orioles |
E4233
|
entity |
| Predicate | team1FoundedAsCurrentName |
P8278
|
FINISHED |
| Object | 1913 |
—
|
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: 1913 | Statement: [New York Yankees vs Baltimore Orioles, team1FoundedAsCurrentName, 1913]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team1FoundedAsCurrentName Context triple: [New York Yankees vs Baltimore Orioles, team1FoundedAsCurrentName, 1913]
-
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.
team1LaterKnownAs
Indicates that the first team was later renamed to or became known by the identity of the second team.
-
D.
departmentFormed
Indicates that a specific department has been created or established, often at a particular time or under certain conditions.
-
E.
formerTeam2Name
Indicates that an entity was previously associated with a second former team identified by this name.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c705fd88190bfee7f5e1f7cee17 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5617788190814358aee3f7ae37 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25c2bda788190bcfc0bc94686f9e0 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.