Triple
T260503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1916 World Series |
E5529
|
entity |
| Predicate | reasonForBravesFieldUse |
P3364
|
FINISHED |
| Object | larger seating capacity than Fenway Park |
—
|
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: larger seating capacity than Fenway Park | Statement: [1916 World Series, reasonForBravesFieldUse, larger seating capacity than Fenway Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForBravesFieldUse Context triple: [1916 World Series, reasonForBravesFieldUse, larger seating capacity than Fenway Park]
-
A.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
B.
selectionReason
chosen
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
C.
hasNotableFieldOfBearers
Indicates that the entities share a significant or distinguished area of activity, expertise, or achievement associated with their bearers.
-
D.
reasonForCreation
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
E.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25f921c2881908821ca2c03815eae |
completed | Feb. 28, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69a25b6b3ea88190bbd858999e42efae |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.