Triple
T17957225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klingons |
E448983
|
entity |
| Predicate | physiologyFeature |
P58263
|
FINISHED |
| Object | redundant organs |
—
|
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: redundant organs | Statement: [Klingons, physiologyFeature, redundant organs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physiologyFeature Context triple: [Klingons, physiologyFeature, redundant organs]
-
A.
physiology
chosen
Indicates that one entity is related to another through biological or bodily functions, processes, or physiological characteristics.
-
B.
biologicalCharacteristic
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
C.
anatomicalFeature
Indicates that one entity is an anatomical part, structure, or feature of another entity.
-
D.
oxygenPhysiology
Indicates the physiological processes, functions, or effects involving oxygen in an organism.
-
E.
cellBiologyFeature
Indicates a relationship where a biological entity possesses or is characterized by a specific cellular-level property, structure, 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afb0afe08190964e771ec632fa1e |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.