Triple
T20612164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fraternité arc |
E506472
|
entity |
| Predicate | hasOrbitalBody |
P11957
|
FINISHED |
| Object | central body Neptune |
—
|
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: central body Neptune | Statement: [Fraternité arc, hasOrbitalBody, central body Neptune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalBody Context triple: [Fraternité arc, hasOrbitalBody, central body Neptune]
-
A.
orbitedBody
chosen
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
-
B.
hasOrbitalCharacteristic
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
-
C.
hasAxisOfOrbit
Indicates that an orbiting object is associated with a specific axis around which its orbital motion is defined.
-
D.
hasCentralBodyRole
Indicates that an entity serves as the primary or central functional component within a larger body or system.
-
E.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad81bdc8190aa6f6164f406a468 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.