Triple
T6810698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal League |
E156623
|
entity |
| Predicate | timelinePosition |
P8810
|
FINISHED |
| Object | operated between Deadball Era and pre–live-ball era changes |
—
|
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: operated between Deadball Era and pre–live-ball era changes | Statement: [Federal League, timelinePosition, operated between Deadball Era and pre–live-ball era changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timelinePosition Context triple: [Federal League, timelinePosition, operated between Deadball Era and pre–live-ball era changes]
-
A.
positionInTimeScale
chosen
Indicates the specific point or interval an event or state occupies within a defined temporal scale or timeline.
-
B.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
-
C.
positionStartTime
Indicates the time at which a position, role, or placement begins.
-
D.
cyclePosition
Indicates the relative location or order of something within a repeating or cyclical sequence.
-
E.
currentPosition
Indicates the present role, job, or status an entity currently holds within a given context.
- 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_69c68828b26c819090fe9df7612bbc27 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30ded6481908fd64611607c610e |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.