Triple
T29209713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Neeyutnee |
E740511
|
entity |
| Predicate | associatedPlanetarySystem |
P174509
|
FINISHED |
| Object | Naboo system |
E421856
|
NE 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: Naboo system | Statement: [Queen Neeyutnee, associatedPlanetarySystem, Naboo system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPlanetarySystem Context triple: [Queen Neeyutnee, associatedPlanetarySystem, Naboo system]
-
A.
otherPlanetsInSystem
Indicates that the referenced planetary system contains one or more planets in addition to the primary or currently considered planet.
-
B.
isInPlanetarySystem
chosen
Indicates that one celestial object is located within and belongs to a particular planetary system.
-
C.
associatedPlanet
Indicates a relationship where one entity is linked or connected to a particular planet, typically as its relevant or corresponding planetary body.
-
D.
suspectedPlanetarySystem
Indicates that an astronomical object is believed, based on available evidence, to host one or more planets but has not yet been confirmed as a planetary system.
-
E.
hasStarSystem
Indicates that an entity possesses, contains, or is associated with a particular star system.
- F. None of above.
Provenance (4 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a0316136a14819085bb88563d5abc42 |
completed | May 12, 2026, 11:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26614429ac8190a05e1b8a999bdf5e |
completed | June 8, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_6a03158a962c81909f17d58197f6ba00 |
completed | May 12, 2026, 11:56 a.m. |
Created at: April 28, 2026, 12:10 p.m.