Triple
T12513841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baseball5 |
E299146
|
entity |
| Predicate | gameStructure |
P34106
|
FINISHED |
| Object | five innings |
—
|
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: five innings | Statement: [Baseball5, gameStructure, five innings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameStructure Context triple: [Baseball5, gameStructure, five innings]
-
A.
actStructure
chosen
Indicates a structural or organizational relationship that defines how an action or activity is arranged, composed, or internally organized.
-
B.
plannedStructure
Indicates that one entity is a structure that is intended or designed to be built or established in the future, rather than already existing.
-
C.
displayStructure
Indicates that one entity presents or reveals the internal organization, layout, or arrangement of another entity.
-
D.
seriesStructure
Indicates how parts or installments are organized and related within a larger series or sequence.
-
E.
raceStructure
Indicates a structural or organizational relationship that defines how a race (such as a competition or contest) is arranged, configured, or composed.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.