Triple
T6778331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994 American League Championship Series |
E155614
|
entity |
| Predicate | expectedFormat |
P130
|
FINISHED |
| Object | best-of-seven series |
—
|
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 series | Statement: [1994 American League Championship Series, expectedFormat, best-of-seven series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedFormat Context triple: [1994 American League Championship Series, expectedFormat, best-of-seven series]
-
A.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
-
B.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
-
C.
overseesFormat
Indicates that one entity is responsible for supervising, managing, or controlling the format or formatting standards of another entity.
-
D.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
includeFormat
Indicates that one entity contains or specifies the format or representation type of another entity.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2689d408190bc2c1ce4ae9c1b13 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.