Triple
T20391778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andoria |
E498101
|
entity |
| Predicate | nativeSpeciesCharacteristic |
P40326
|
FINISHED |
| Object | blue-skinned inhabitants |
—
|
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: blue-skinned inhabitants | Statement: [Andoria, nativeSpeciesCharacteristic, blue-skinned inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeSpeciesCharacteristic Context triple: [Andoria, nativeSpeciesCharacteristic, blue-skinned inhabitants]
-
A.
characteristicTaxon
Indicates that one taxon is characteristic or typical of another taxonomic group, such as serving as a defining or representative member.
-
B.
faunaCharacteristic
Indicates that an entity has a specific trait, feature, or quality related to animals or animal life.
-
C.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
D.
biologicalCharacteristic
chosen
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
E.
lifeCharacteristic
Indicates that an entity possesses a particular trait, feature, or quality relevant to its life or living state.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e679108b1481909677cf80e8e77e76 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.