Triple
T29768149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Cross region |
E753971
|
entity |
| Predicate | hasMainConstellation |
P9993
|
FINISHED |
| Object | Crux |
—
|
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: Crux | Statement: [Southern Cross region, hasMainConstellation, Crux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainConstellation Context triple: [Southern Cross region, hasMainConstellation, Crux]
-
A.
usesConstellation
Indicates that one entity makes use of, relies on, or incorporates a particular constellation in its function, representation, or operation.
-
B.
parentConstellation
Indicates that one constellation is the larger or primary constellation within which another constellation is contained or of which it is a part.
-
C.
isDistinctiveConstellation
Indicates that a constellation stands out from others due to unique or distinguishing characteristics.
-
D.
hasMainAsterismShape
Indicates that an entity is associated with a specific primary asterism shape that characterizes its overall pattern or outline.
-
E.
relatedConstellation
chosen
Indicates a relationship where one entity is associated with, connected to, or corresponds to a particular constellation.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: April 28, 2026, 8:39 p.m.