Triple
T4830762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Climax Series |
E107938
|
entity |
| Predicate | firstStageFormat |
P30244
|
FINISHED |
| Object | best-of-three 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-three series | Statement: [Climax Series, firstStageFormat, best-of-three series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstStageFormat Context triple: [Climax Series, firstStageFormat, best-of-three series]
-
A.
firstStageType
Indicates that one entity is the type or category of the first stage or initial phase associated with another entity.
-
B.
firstStageName
Indicates that one entity is the initial or earliest stage name associated with another entity in a sequence or lifecycle.
-
C.
firstPartFormat
chosen
Indicates that the subject entity is the initial segment or portion in the overall format or structured sequence of something.
-
D.
firstStageDescription
Indicates that the value provides a textual explanation or summary of the initial or earliest stage in a multi-stage process or sequence.
-
E.
firstStageEngine
Indicates that an engine functions as the primary propulsion unit used in the first stage of a multi-stage launch vehicle or rocket.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.