Triple
T16096396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashyyyk |
E390493
|
entity |
| Predicate | lowerLevels |
P48833
|
FINISHED |
| Object | dangerous wildlife |
—
|
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: dangerous wildlife | Statement: [Kashyyyk, lowerLevels, dangerous wildlife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerLevels Context triple: [Kashyyyk, lowerLevels, dangerous wildlife]
-
A.
lowerLevelServes
Indicates that a lower-level component, service, or entity provides functionality or support to a higher-level component, service, or entity.
-
B.
lowerStage
Indicates that one entity is at a lower or earlier stage, level, or phase in a progression or hierarchy than another entity.
-
C.
lowerLocation
chosen
Indicates that one entity is located physically below or at a lower vertical position relative to another entity.
-
D.
lowerLevelUsedFor
Indicates that a lower-level component, resource, or abstraction is utilized to implement, support, or realize the functionality of a higher-level one.
-
E.
lowerRank
Indicates that one entity holds an inferior or subordinate rank, status, or position relative to another entity.
- 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.