Triple
T5789367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager |
E128352
|
entity |
| Predicate | hasClassDesignation |
P974
|
FINISHED |
| Object | Class 220 |
—
|
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: Class 220 | Statement: [Voyager, hasClassDesignation, Class 220]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClassDesignation Context triple: [Voyager, hasClassDesignation, Class 220]
-
A.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
-
B.
hasDesignation
chosen
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
C.
hasLetterDesignation
Indicates that an entity is assigned or associated with a specific letter-based designation or code.
-
D.
hasPortionDesignatedAs
Indicates that one entity has a specific part or segment that is explicitly identified or designated as another entity.
-
E.
hasDesignationNearby
Indicates that one entity has a designation (such as a label, title, or marker) located in close physical or contextual proximity to 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a53d0148190bdebc4f5609939ac |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.