Triple
T6395817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 23 Tauri |
E143937
|
entity |
| Predicate | hasGalacticCoordinateSystem |
P70378
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [23 Tauri, hasGalacticCoordinateSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGalacticCoordinateSystem Context triple: [23 Tauri, hasGalacticCoordinateSystem, yes]
-
A.
hasGalacticContext
Indicates that something is associated with, situated within, or characterized by a broader galactic-scale environment or framework.
-
B.
positionRelativeToGalacticCenter
Indicates the spatial location of an entity expressed in relation to the center of its galaxy.
-
C.
isInGalaxy
Indicates that one astronomical object is located within or belongs to a particular galaxy.
-
D.
containsGalaxy
Indicates that one entity spatially includes or encompasses a galaxy as part of its contents or structure.
-
E.
astronomicalSystem
Indicates a relationship in which multiple astronomical objects are organized into a coherent physical or dynamical system (such as a planetary system, star system, or galaxy).
- F. None of above. chosen
Provenance (4 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0688275d0819086b58123c743a6db |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:35 p.m.