Triple
T4168219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expansion Era Committee |
E84494
|
entity |
| Predicate | eraDefinition |
P54472
|
FINISHED |
| Object | post-1972 Major League Baseball period |
—
|
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: post-1972 Major League Baseball period | Statement: [Expansion Era Committee, eraDefinition, post-1972 Major League Baseball period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraDefinition Context triple: [Expansion Era Committee, eraDefinition, post-1972 Major League Baseball period]
-
A.
eraType
Indicates the classification of a time period or era according to its type or category.
-
B.
era
Indicates that something existed, occurred, or was valid during a specified historical or temporal period.
-
C.
eraEnd
Indicates the point in time or event at which a particular era, period, or phase comes to a close.
-
D.
eraSystem
Indicates a temporal classification relationship where an entity is associated with a particular era or chronological system used to organize time.
-
E.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c573788190a60ab3f83b07a6f6 |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af01ee94ec8190aa6dde54d4571c04 |
completed | March 9, 2026, 5:22 p.m. |
Created at: March 9, 2026, 3:44 p.m.