Triple
T16611389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wookiee |
E403576
|
entity |
| Predicate | notableLocationOnHomeworld |
P123531
|
FINISHED |
| Object | wroshyr tree cities |
—
|
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: wroshyr tree cities | Statement: [Wookiee, notableLocationOnHomeworld, wroshyr tree cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLocationOnHomeworld Context triple: [Wookiee, notableLocationOnHomeworld, wroshyr tree cities]
-
A.
homeworldLocation
Indicates the relationship between an entity and the specific place or celestial body that serves as its homeworld.
-
B.
notableGameLocation
Indicates that a particular place is recognized as a significant or prominent location within a game.
-
C.
isPrimarySpaceportOf
Indicates that a given spaceport serves as the main or principal launch and operations facility for a specified region, organization, or celestial body.
-
D.
planetOfLocation
Indicates that a planet is the astronomical body on which or around which a given location is situated.
-
E.
residencePlanet
Indicates that an entity’s primary place of residence is located on a specified planet.
- F. None of above. chosen
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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e36096356c819092815d64db041793 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.