Triple
T6694952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phalangeriformes |
E152724
|
entity |
| Predicate | hasLowerIncisors |
P35359
|
FINISHED |
| Object | two large forward‑projecting lower incisors (diprotodont dentition) in most species |
—
|
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: two large forward‑projecting lower incisors (diprotodont dentition) in most species | Statement: [Phalangeriformes, hasLowerIncisors, two large forward‑projecting lower incisors (diprotodont dentition) in most species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerIncisors Context triple: [Phalangeriformes, hasLowerIncisors, two large forward‑projecting lower incisors (diprotodont dentition) in most species]
-
A.
hasTeeth
Indicates that one entity possesses teeth as a physical feature.
-
B.
incisorCount
Indicates the number of incisor teeth an entity has.
-
C.
dentition
chosen
Indicates the type, arrangement, or condition of teeth that an entity possesses.
-
D.
hasLowerBarLength
Indicates that one entity’s bar length is shorter than the bar length of another entity.
-
E.
hasMandibles
Indicates that an entity possesses mandibles, i.e., jaw-like mouthparts used for biting, cutting, or holding.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6b5ed99e48190970805225458ce82 |
completed | March 27, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0e1d348190af1762ea1951038e |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:05 p.m.