Triple
T13117569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robison Field |
E311133
|
entity |
| Predicate | homeTeamDuration |
P108132
|
FINISHED |
| Object | longtime home of the St. Louis Cardinals |
—
|
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: longtime home of the St. Louis Cardinals | Statement: [Robison Field, homeTeamDuration, longtime home of the St. Louis Cardinals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamDuration Context triple: [Robison Field, homeTeamDuration, longtime home of the St. Louis Cardinals]
-
A.
homeTeamUntil
Indicates that an entity serves as the home team for another entity up to (but not necessarily after) a specified time or event.
-
B.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
C.
locationTeam2Home
Indicates that the specified location serves as the home venue or home ground for the second team involved in the context.
-
D.
stateOfHomeTeam2
Indicates the current status or condition of the second home team in a given context or event.
-
E.
locationTeam1Home
Indicates that the specified location serves as the home venue or home ground for team 1 in the relationship.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98182011c8190a504678affbb7787 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98134df64819084a5674f9475dcc2 |
completed | April 10, 2026, 11:01 p.m. |
Created at: April 9, 2026, 9:06 p.m.