Triple
T20612607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirzam |
E506483
|
entity |
| Predicate | locationRelativeToSirius |
P9990
|
FINISHED |
| Object | near Sirius in the winter sky |
—
|
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: near Sirius in the winter sky | Statement: [Mirzam, locationRelativeToSirius, near Sirius in the winter sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeToSirius Context triple: [Mirzam, locationRelativeToSirius, near Sirius in the winter sky]
-
A.
positionInConstellation
Indicates the specific location or role an object occupies within the boundaries or structure of a given constellation.
-
B.
locationOnTelescope
Indicates that one entity is positioned at or attached to a specific part or place on a telescope.
-
C.
positionRelativeToAndromeda
Indicates the spatial location or orientation of an entity in relation to the Andromeda galaxy.
-
D.
positionRelativeToEarth
Indicates the spatial position or orientation of an entity in relation to the Earth as a reference frame.
-
E.
celestialLocation
chosen
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad94dac8190921c7769a649c724 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.