Triple
T19260982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydrus |
E481647
|
entity |
| Predicate | liesInMilkyWayRegion |
P9997
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Hydrus, liesInMilkyWayRegion, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesInMilkyWayRegion Context triple: [Hydrus, liesInMilkyWayRegion, false]
-
A.
locatedInMilkyWayArm
Indicates that one entity is situated within a specific spiral arm of the Milky Way galaxy in which the other entity (the arm) is defined.
-
B.
isInGalaxy
Indicates that one astronomical object is located within or belongs to a particular galaxy.
-
C.
locatedInSkyRegion
chosen
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
D.
galacticNeighborhood
Indicates a spatial relationship where one astronomical object or system is located in the nearby region or vicinity of another within a galaxy or local group of galaxies.
-
E.
isSatelliteGalaxyOf
Indicates that one galaxy orbits and is gravitationally bound to another, larger host galaxy as its satellite.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb890e7c8190beba407f63459382 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.