Triple
T28495820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elephantulus |
E721103
|
entity |
| Predicate | hasSnoutType |
P56645
|
FINISHED |
| Object | elongated flexible proboscis-like snout |
—
|
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: elongated flexible proboscis-like snout | Statement: [Elephantulus, hasSnoutType, elongated flexible proboscis-like snout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSnoutType Context triple: [Elephantulus, hasSnoutType, elongated flexible proboscis-like snout]
-
A.
snoutType
chosen
Indicates the type or form of an entity’s snout in relation to its overall morphology.
-
B.
haveSnouts
Indicates that the subject possesses or is characterized by snouts.
-
C.
hasSnoutAdaptation
Indicates that an entity possesses a specific modification or specialized feature of its snout adapted for a particular function or environment.
-
D.
hasTypeOfMouth
Indicates that an entity possesses a mouth characterized by a specific type or form.
-
E.
hasNoseExtension
Indicates that one entity possesses or is characterized by an extension or protruding part of the nose.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 3:04 a.m.