Triple
T2316643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League Championship Series |
E51079
|
entity |
| Predicate | introducedFormat |
P513
|
FINISHED |
| Object | best-of-seven in 1985 |
—
|
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: best-of-seven in 1985 | Statement: [League Championship Series, introducedFormat, best-of-seven in 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedFormat Context triple: [League Championship Series, introducedFormat, best-of-seven in 1985]
-
A.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
B.
introduced
chosen
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
singleMatchFormatIntroduced
Indicates that a particular single-match competition format was introduced or first implemented.
-
D.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
E.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.