Triple
T26412643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tethys Trojan moons |
E664001
|
entity |
| Predicate | areLocatedAt |
P160528
|
FINISHED |
| Object | L4 and L5 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: L4 and L5 Lagrange points of Tethys | Statement: [Tethys Trojan moons, areLocatedAt, L4 and L5 Lagrange points of Tethys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areLocatedAt Context triple: [Tethys Trojan moons, areLocatedAt, L4 and L5 Lagrange points of Tethys]
-
A.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
organizationLocatedAt
Indicates that an organization is situated or based at a specific geographic location or address.
-
D.
collectivelyLocatedIn
Indicates that multiple entities are all located within the same place or spatial region considered as a group.
-
E.
agencyLocatedIn
Indicates that an agency is situated or based within a specific geographic or administrative location.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f611325fd48190898639883fb113fd |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:39 p.m.