Triple
T3515486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turner Field |
E74296
|
entity |
| Predicate | postBravesConversion |
P48475
|
FINISHED |
| Object | college football stadium |
—
|
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: college football stadium | Statement: [Turner Field, postBravesConversion, college football stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postBravesConversion Context triple: [Turner Field, postBravesConversion, college football stadium]
-
A.
conversionProcess
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
-
B.
convertedBy
Indicates that one entity has been transformed or changed in form, state, or representation through the action or process performed by another entity.
-
C.
broughtTo
Indicates that one entity caused another entity or object to be transported or accompanied to a particular destination or recipient.
-
D.
conversionCompleted
Indicates that a previously initiated conversion process has finished successfully.
-
E.
convertsTo
Indicates that one entity is transformed or changed into another entity, typically resulting in a different state, form, or representation.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc30362c81908ca7497a6a935cc6 |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:19 p.m.