Triple
T1997675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moschidae |
E43394
|
entity |
| Predicate | lacksTrait |
P13714
|
FINISHED |
| Object | antlers in both sexes |
—
|
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: antlers in both sexes | Statement: [Moschidae, lacksTrait, antlers in both sexes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lacksTrait Context triple: [Moschidae, lacksTrait, antlers in both sexes]
-
A.
doesNotHave
Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
-
B.
typicallyLack
chosen
Indicates that one entity is characteristically or usually without, or does not possess, another entity or attribute.
-
C.
logicalTrait
Indicates that an entity possesses a characteristic, behavior, or quality related to logical reasoning or structured thinking.
-
D.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
E.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.