Triple
T29209651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neimoidian |
E740510
|
entity |
| Predicate | notablePhysicalTrait |
P200117
|
FINISHED |
| Object | elongated heads |
—
|
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: elongated heads | Statement: [Neimoidian, notablePhysicalTrait, elongated heads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePhysicalTrait Context triple: [Neimoidian, notablePhysicalTrait, elongated heads]
-
A.
hasPhysicalFeature
Indicates that one entity possesses or exhibits a specific physical characteristic or feature of another entity.
-
B.
notableRaceCharacteristic
Indicates that an entity is distinguished by a particular race-related trait or attribute that is especially prominent or noteworthy.
-
C.
hasParticularNotableCharacteristic
Indicates that an entity possesses a specific, noteworthy characteristic or quality that distinguishes it in some relevant context.
-
D.
notableAppearanceFeature
chosen
Indicates that an entity is characterized by a distinctive or noteworthy physical appearance trait.
-
E.
rimCharacteristic
Indicates a specific property or feature that characterizes a rim in the context of its structure, design, or function.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a031b40c6d0819096f4b9787a1f09d1 |
completed | May 12, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_6a03191f8ee08190b3416b044869ddfd |
completed | May 12, 2026, 12:12 p.m. |
Created at: April 28, 2026, 12:10 p.m.