Triple
T36411047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boss Nass |
E896878
|
entity |
| Predicate | speciesVariant |
P17197
|
FINISHED |
| Object | ankura Gungan |
—
|
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: ankura Gungan | Statement: [Boss Nass, speciesVariant, ankura Gungan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesVariant Context triple: [Boss Nass, speciesVariant, ankura Gungan]
-
A.
relatedSpeciesOrVariant
chosen
Indicates that one species or biological variant is taxonomically or genetically related to another.
-
B.
specificCarrierVariant
Indicates that one entity is a particular, more narrowly defined version or subtype of a broader carrier entity.
-
C.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
D.
denotesVariantOf
Indicates that one entity is a variant or alternative form of another, typically sharing core identity or function with some differences.
-
E.
customizedVariantOf
Indicates that one entity is a modified or tailored version derived from another, preserving a core basis while introducing specific customizations.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.