Triple
T29860483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5668 Foucault |
E758298
|
entity |
| Predicate | isInOrbitAround |
P11957
|
FINISHED |
| Object | Sun |
—
|
NE NERFINISHED |
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 | Statement: [5668 Foucault, isInOrbitAround, Sun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInOrbitAround Context triple: [5668 Foucault, isInOrbitAround, Sun]
-
A.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
B.
isBeyondOrbitOf
Indicates that one object follows an orbital path that lies entirely outside or farther from the central body than the orbit of another object.
-
C.
isOnOrbital
Indicates that one entity is located on or traveling along the orbital path associated with another entity.
-
D.
includesOrbitOf
Indicates that one entity’s orbital path or region fully contains or encompasses the orbital path or region of another entity.
-
E.
orbitedBody
chosen
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67684c1fc8190863407fee93628b9 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:48 p.m.