Triple
T24734737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 Division Series |
E618378
|
entity |
| Predicate | temporaryFormat |
P157065
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1981 Division Series, temporaryFormat, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporaryFormat Context triple: [1981 Division Series, temporaryFormat, true]
-
A.
temFormato
Indicates that one entity has, uses, or conforms to a specific format defined by another entity.
-
B.
temporaryLocation
Indicates that an entity is located at a place for a limited or non-permanent duration.
-
C.
temporaryNameOf
Indicates that one entity serves as a provisional or interim name assigned to another entity, intended to be replaced by a permanent name later.
-
D.
temporaryStructureFor
Indicates that one entity serves as a non-permanent or provisional structure intended to support, house, or substitute for another entity.
-
E.
temporalForm
Indicates a relationship where one entity represents the specific temporal version, state, or form that another entity takes at a particular time.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:03 a.m.