Triple
T26412642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tethys Trojan moons |
E664001
|
entity |
| Predicate | resideNear |
P41003
|
FINISHED |
| Object | Lagrange points of Tethys |
—
|
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: Lagrange points of Tethys | Statement: [Tethys Trojan moons, resideNear, Lagrange points of Tethys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resideNear Context triple: [Tethys Trojan moons, resideNear, Lagrange points of Tethys]
-
A.
residesNear
chosen
Indicates that one entity lives or is located in close physical proximity to another entity.
-
B.
believedToResideIn
Indicates that one entity is thought or assumed to live or be located in a particular place or region, without confirming this as a verified fact.
-
C.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
D.
residencyOf
Indicates that one entity serves as the place where another entity resides or lives.
-
E.
residesOver
Indicates that one entity lives or is situated in a position physically higher than or above 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 26, 2026, 11:39 p.m.