Triple
T34957474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miral (Klingon mother) |
E1008157
|
entity |
| Predicate | bloodQuantum |
P22696
|
FINISHED |
| Object | full-blooded Klingon |
—
|
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: full-blooded Klingon | Statement: [Miral (Klingon mother), bloodQuantum, full-blooded Klingon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodQuantum Context triple: [Miral (Klingon mother), bloodQuantum, full-blooded Klingon]
-
A.
bloodStatus
chosen
Indicates the classification of an entity based on the type or purity of its blood or lineage.
-
B.
bloodRageStatus
Indicates a temporary state in which an entity is overcome by extreme, often uncontrollable, rage or bloodlust.
-
C.
hasBlood
Indicates that one entity possesses or contains the blood of another entity.
-
D.
bloodMixedWith
Indicates that the blood of one entity is combined or intermixed with the blood of another entity.
-
E.
bloodTrait
Indicates that one entity has a specific blood-related characteristic, property, or attribute associated with 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.