Triple
T5723564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alnitak |
E126206
|
entity |
| Predicate | positionInOrionsBelt |
P32060
|
FINISHED |
| Object | easternmost 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: easternmost star | Statement: [Alnitak, positionInOrionsBelt, easternmost star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInOrionsBelt Context triple: [Alnitak, positionInOrionsBelt, easternmost star]
-
A.
positionInRingSystem
Indicates the specific location or ordering of an object within a ring system relative to the system’s central body and/or other ring components.
-
B.
partOfConstellation
chosen
Indicates that one entity is a component or member star/feature within the larger grouping defined as a specific constellation.
-
C.
positionInCosmos
Indicates the spatial or hierarchical location of an entity within the broader structure of the cosmos or universe.
-
D.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
E.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c6488881909bed4a4534d57f70 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:46 p.m.