Triple
T20478862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uranian system |
E502397
|
entity |
| Predicate | hasCentralBodyType |
P27402
|
FINISHED |
| Object | ice giant |
—
|
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: ice giant | Statement: [Uranian system, hasCentralBodyType, ice giant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralBodyType Context triple: [Uranian system, hasCentralBodyType, ice giant]
-
A.
hasCentralBodyRole
Indicates that an entity serves as the primary or central functional component within a larger body or system.
-
B.
hasCentralStarType
Indicates that one entity (typically a planetary system) is associated with or characterized by a central star of a specified stellar type.
-
C.
centralBody
chosen
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
D.
hasCentralStar
Indicates that an astronomical system or structure possesses a primary star located at its center.
-
E.
orbitalBodyType
Indicates the classification of an orbital body in terms of its type (e.g., planet, moon, asteroid, comet) within an orbital system.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b54c8188190a71e35fab8d194a6 |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.