Triple
T23000230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libra |
E572612
|
entity |
| Predicate | iausDesignation |
P30509
|
FINISHED |
| Object | IAU-recognized constellation |
—
|
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: IAU-recognized constellation | Statement: [Libra, iausDesignation, IAU-recognized constellation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iausDesignation Context triple: [Libra, iausDesignation, IAU-recognized constellation]
-
A.
internationalDesignation
chosen
Indicates that an entity has been assigned a formal status, code, or recognition by an international body or under an internationally agreed system.
-
B.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
C.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
-
D.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
E.
stateDesignation
Indicates that an entity has been formally assigned or recognized with a particular status, title, or classification by an official authority or governing body.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18352bcf48190bd474eff69b3465b |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.