Triple
T23850106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurus II |
E592137
|
entity |
| Predicate | secondStageVariant |
P37035
|
FINISHED |
| Object | Castor 30 |
—
|
NE NERFINISHED |
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: Castor 30 | Statement: [Taurus II, secondStageVariant, Castor 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondStageVariant Context triple: [Taurus II, secondStageVariant, Castor 30]
-
A.
secondStageType
chosen
Indicates the specific kind or category of a process, object, or event that occurs as the second stage in a multi-stage sequence.
-
B.
secondStage
Indicates that something functions as the subsequent or follow-up stage in a multi-stage process or sequence.
-
C.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
-
D.
secondVersion
Indicates that one entity is a later or updated second version of another entity.
-
E.
secondStageDescription
Indicates that the predicate provides a textual explanation or details about the second stage of a multi-stage process or sequence.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c986f7e08190a6d361423946ff05 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.