Triple
T34968796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazon-Ogla |
E1008476
|
entity |
| Predicate | notableMemberSpecies |
P47321
|
FINISHED |
| Object | Kazon male warriors |
—
|
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: Kazon male warriors | Statement: [Kazon-Ogla, notableMemberSpecies, Kazon male warriors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMemberSpecies Context triple: [Kazon-Ogla, notableMemberSpecies, Kazon male warriors]
-
A.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
B.
notableMemberTaxon
Indicates that a taxonomic group has a particular member taxon that is especially notable or representative within that group.
-
C.
notablePetMember
Indicates that one entity is a pet that is notably associated with, or recognized as belonging to, another entity.
-
D.
notableSpeciesGroup
chosen
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
E.
commonNameOfNotableSpecies
Indicates that the subject is a commonly used vernacular or everyday name for a notable or well-known biological species.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.