Triple
T26305207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asterope II |
E661661
|
entity |
| Predicate | hasTraditionalDesignation |
P17611
|
FINISHED |
| Object | Asterope |
—
|
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: Asterope | Statement: [Asterope II, hasTraditionalDesignation, Asterope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalDesignation Context triple: [Asterope II, hasTraditionalDesignation, Asterope]
-
A.
historicalDesignation
Indicates that an entity has been formally assigned a particular status, title, or classification based on its historical significance.
-
B.
hasHereditaryDesignation
Indicates that an entity possesses a title, status, or designation that is passed down through family lineage or inheritance.
-
C.
hasTraditionalName
chosen
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
D.
hasDiscoveryDesignation
Indicates that an entity has been assigned a specific designation or label associated with its discovery.
-
E.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 26, 2026, 10:18 p.m.