Triple
T8498225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naboo |
E201150
|
entity |
| Predicate | planetClass |
P62562
|
FINISHED |
| Object | terrestrial |
—
|
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: terrestrial | Statement: [Naboo, planetClass, terrestrial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetClass Context triple: [Naboo, planetClass, terrestrial]
-
A.
hostPlanetType
chosen
Indicates the type or classification of the planet that serves as the host in the relationship.
-
B.
majorBody
Indicates that one entity is the primary or most significant body (e.g., celestial, organizational, or governing body) in relation to another entity.
-
C.
innerPlanetOf
Indicates that one celestial body orbits closer to the central star than another body within the same planetary system.
-
D.
associatedPlanet
Indicates a relationship where one entity is linked or connected to a particular planet, typically as its relevant or corresponding planetary body.
-
E.
hasPlanet
Indicates that one entity possesses, contains, or is associated with a particular planet as part of its system or domain.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe583aebc819090345684bfa1fca2 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.