Triple
T20326732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tucana |
E492358
|
entity |
| Predicate | celestialLongitudeRegion |
P9990
|
FINISHED |
| Object | southernSky |
—
|
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: southernSky | Statement: [Tucana, celestialLongitudeRegion, southernSky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celestialLongitudeRegion Context triple: [Tucana, celestialLongitudeRegion, southernSky]
-
A.
lunarLongitude
Indicates the angular position of the Moon along its orbital path, measured as longitude relative to a defined reference direction or point.
-
B.
eclipticLongitudeRange
Indicates that an entity’s ecliptic longitude lies within a specified angular range along the ecliptic.
-
C.
celestialLocation
chosen
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
D.
galacticLongitudeRange
Indicates the span of galactic longitudes over which an object, event, or region is defined or observed.
-
E.
solarSystemRegion
Indicates that one entity is a region or area located within the solar system that is associated with or contains the other entity.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e4130081909ec54f131939e442 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:21 a.m.