Triple
T32170015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth–Moon barycenter |
E821684
|
entity |
| Predicate | liesOnLineBetween |
P173660
|
FINISHED |
| Object | Earth center |
—
|
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: Earth center | Statement: [Earth–Moon barycenter, liesOnLineBetween, Earth center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesOnLineBetween Context triple: [Earth–Moon barycenter, liesOnLineBetween, Earth center]
-
A.
liegtAm
Indicates that one entity is located on, by, or along another entity (such as a place lying on a river, coast, or route).
-
B.
liesIn
Indicates that one entity is located within the spatial, geographical, or conceptual boundaries of another entity.
-
C.
liesOnBorderOf
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
D.
isJunctionOnLine
Indicates that a particular junction lies on, or is part of, a specified line.
-
E.
isBetweenStationsOnLine
Indicates that something is located or occurs between two stations along the same transit line.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba73aa9c819082328ddf6ec799ec |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:33 a.m.