Triple
T15120334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elephantidae |
E361153
|
entity |
| Predicate | sensoryCharacteristic |
P56672
|
FINISHED |
| Object | high intelligence |
—
|
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: high intelligence | Statement: [Elephantidae, sensoryCharacteristic, high intelligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensoryCharacteristic Context triple: [Elephantidae, sensoryCharacteristic, high intelligence]
-
A.
fruitCharacteristic
Indicates that a specified characteristic or property is attributed to a particular fruit.
-
B.
fleshCharacteristic
Indicates that one entity has a particular property, quality, or attribute of its flesh (such as texture, color, or condition) in relation to another entity or value.
-
C.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
D.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
E.
describesCharacteristicOf
chosen
Indicates that one entity expresses or specifies a characteristic, feature, or property of 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059e036c8190959ff3bde8f2356f |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.