Triple
T16096340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloud City |
E390492
|
entity |
| Predicate | planetTypeOfLocation |
P62562
|
FINISHED |
| Object | gas 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: gas giant | Statement: [Cloud City, planetTypeOfLocation, gas giant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetTypeOfLocation Context triple: [Cloud City, planetTypeOfLocation, gas giant]
-
A.
hostPlanetType
chosen
Indicates the type or classification of the planet that serves as the host in the relationship.
-
B.
cosmicLocationType
Indicates the specific kind of spatial or cosmic setting in which an entity or event is situated (e.g., galaxy, nebula, star system).
-
C.
hasPlanetaryFeatureType
Indicates that an entity possesses or is associated with a specific type of planetary surface or geological feature.
-
D.
residencePlanet
Indicates that an entity’s primary place of residence is located on a specified planet.
-
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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.