Triple
T206980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merope |
E4629
|
entity |
| Predicate | locatedInSkyRegion |
P9997
|
FINISHED |
| Object | near the ecliptic in Taurus |
—
|
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 the ecliptic in Taurus | Statement: [Merope, locatedInSkyRegion, near the ecliptic in Taurus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSkyRegion Context triple: [Merope, locatedInSkyRegion, near the ecliptic in Taurus]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
C.
galacticCenterConstellation
Indicates the constellation in which the center of a given galaxy is located.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
telescopeLocation
Indicates the physical place or site where a telescope is situated or installed.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25e292fdc8190bfd51d8848f9ed58 |
completed | Feb. 28, 2026, 3:16 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.