Triple
T23516338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miller’s planet |
E574378
|
entity |
| Predicate | gravitationalSource |
P27402
|
FINISHED |
| Object | Gargantua |
—
|
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: Gargantua | Statement: [Miller’s planet, gravitationalSource, Gargantua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gravitationalSource Context triple: [Miller’s planet, gravitationalSource, Gargantua]
-
A.
interactsGravitationallyWith
Indicates that one entity exerts a gravitational influence on, and is influenced by, another entity, according to the laws of gravity.
-
B.
gravityFieldStudiedBy
Indicates that a gravity field is the subject of study or analysis by a particular agent or entity.
-
C.
gravityOfBody
Indicates the gravitational influence or field produced by a specific celestial body.
-
D.
centralBody
chosen
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
E.
hasGravitationalPotential
Indicates that one entity possesses gravitational potential energy or capacity relative to another entity or reference frame due to their positions in a gravitational field.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa81ab4c8190b85c8f80754020ea |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:08 p.m.