Triple
T10734749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venus as evening star |
E253163
|
entity |
| Predicate | skyPositionConstraint |
P9990
|
FINISHED |
| Object | never far from the Sun |
—
|
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: never far from the Sun | Statement: [Venus as evening star, skyPositionConstraint, never far from the Sun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skyPositionConstraint Context triple: [Venus as evening star, skyPositionConstraint, never far from the Sun]
-
A.
celestialLocation
chosen
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
B.
orbitalPosition
Indicates the relative location or path of one object in its orbit with respect to a central body or reference frame.
-
C.
positionRelativeToEarth
Indicates the spatial position or orientation of an entity in relation to the Earth as a reference frame.
-
D.
starsPosition
Indicates that one entity specifies the spatial location or coordinates of a star or group of stars relative to a reference frame.
-
E.
inclinationConstraint
Indicates a restriction or condition placed on the allowable angle or tilt between entities or components.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71020e1c881909e40f398de2bdd25 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.