Triple
T4618879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LG |
E100930
|
entity |
| Predicate | gravitationallyBound |
P20406
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LG, gravitationallyBound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gravitationallyBound Context triple: [LG, gravitationallyBound, true]
-
A.
isGravitationallyBound
chosen
Indicates that one object is held in a stable or semi-stable configuration by the gravitational attraction of another (or others), such that it cannot escape without additional energy.
-
B.
interactsGravitationallyWith
Indicates that one entity exerts a gravitational influence on, and is influenced by, another entity, according to the laws of gravity.
-
C.
hasCentralBodyRole
Indicates that an entity serves as the primary or central functional component within a larger body or system.
-
D.
isSatelliteGalaxyOf
Indicates that one galaxy orbits and is gravitationally bound to another, larger host galaxy as its satellite.
-
E.
orbitedBody
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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e247448190ad92f194cb1127c5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.