Triple
T10734778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vesper |
E253164
|
entity |
| Predicate | historicalMisclassification |
P13759
|
FINISHED |
| Object | star |
—
|
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: star | Statement: [Vesper, historicalMisclassification, star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMisclassification Context triple: [Vesper, historicalMisclassification, star]
-
A.
historicalClassificationEnd
Indicates the point in time when a particular historical classification or categorization of an entity ceases to be valid.
-
B.
historicalClassificationStart
Indicates the point in time when a particular historical classification or categorization of an entity begins to apply.
-
C.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
D.
historicallyConsidered
chosen
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
-
E.
historicalIdentificationOf
Indicates that one entity has been identified, classified, or recognized as another entity within a historical context or by historical sources.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71020e1c881909e40f398de2bdd25 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.