Triple
T12175052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun–Earth L2 |
E290065
|
entity |
| Predicate | visibilityProperty |
P9694
|
FINISHED |
| Object | always lies roughly opposite the Sun as seen from Earth |
—
|
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: always lies roughly opposite the Sun as seen from Earth | Statement: [Sun–Earth L2, visibilityProperty, always lies roughly opposite the Sun as seen from Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibilityProperty Context triple: [Sun–Earth L2, visibilityProperty, always lies roughly opposite the Sun as seen from Earth]
-
A.
visibilityStatus
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
-
B.
visibleAt
chosen
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
C.
visibilityComputation
Indicates the process or relationship by which the visibility of one entity from another is determined or computed.
-
D.
visibilityRole
Indicates the role or level of access an entity has in determining what information or content is visible to others.
-
E.
visibilityRequirement
Indicates that one entity must be visible or perceivable under specified conditions for another entity, action, or rule to apply.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.