Triple
T868818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion Arm |
E18764
|
entity |
| Predicate | positionInGalaxy |
P9990
|
FINISHED |
| Object | between Sagittarius Arm and Perseus Arm |
—
|
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: between Sagittarius Arm and Perseus Arm | Statement: [Orion Arm, positionInGalaxy, between Sagittarius Arm and Perseus Arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInGalaxy Context triple: [Orion Arm, positionInGalaxy, between Sagittarius Arm and Perseus Arm]
-
A.
distanceFromGalacticCenter
Indicates the measured or calculated spatial separation between an entity and the center of its galaxy.
-
B.
galacticDestination
Indicates that one entity serves as the target or endpoint location within a galaxy that another entity is directed or traveling toward.
-
C.
distanceToGalacticCenter
Indicates the measured or calculated spatial distance between an entity and the center of its galaxy.
-
D.
celestialLocation
chosen
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
E.
galacticCenterConstellation
Indicates the constellation in which the center of a given galaxy is located.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7f98908190883f71049092c7c8 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa87504481909618a6815948da6f |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.