Triple
T8264694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun–Earth L1 Lagrange point |
E193272
|
entity |
| Predicate | liesOnLineConnecting |
P64784
|
FINISHED |
| Object | Sun and 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: Sun and Earth | Statement: [Sun–Earth L1 Lagrange point, liesOnLineConnecting, Sun and Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesOnLineConnecting Context triple: [Sun–Earth L1 Lagrange point, liesOnLineConnecting, Sun and Earth]
-
A.
liesIn
Indicates that one entity is located within the spatial, geographical, or conceptual boundaries of another entity.
-
B.
liesOnBorderOf
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
C.
isJunctionOnLine
chosen
Indicates that a particular junction lies on, or is part of, a specified line.
-
D.
liesOnEcliptic
Indicates that the referenced object’s position is located on or very close to the plane of the ecliptic.
-
E.
perpendicularTo
Indicates that one entity is oriented at a right angle (90 degrees) to another entity.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb793aa8f08190b20b3616ceb9bec7 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.