Triple
T8392655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macroscelidea |
E197978
|
entity |
| Predicate | hasVernacularMisnomer |
P80396
|
FINISHED |
| Object | elephant shrew |
—
|
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: elephant shrew | Statement: [Macroscelidea, hasVernacularMisnomer, elephant shrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVernacularMisnomer Context triple: [Macroscelidea, hasVernacularMisnomer, elephant shrew]
-
A.
vernacularNameAppliedTo
chosen
Indicates that a particular common or vernacular name is assigned or applied to an entity.
-
B.
hasEthnonymVariant
Indicates that one ethnonym is an alternative or variant form of another ethnonym referring to the same ethnic group.
-
C.
hasExonym
Indicates that one entity is known by an alternative name or designation in another language or cultural context.
-
D.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
E.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8184788081909e9857afff629985 |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.