Triple
T37936980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunder |
E946375
|
entity |
| Predicate | hasCamelSpeciesUsedForSafaris |
P101568
|
FINISHED |
| Object | Bactrian camel |
E224340
|
NE 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: Bactrian camel | Statement: [Hunder, hasCamelSpeciesUsedForSafaris, Bactrian camel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCamelSpeciesUsedForSafaris Context triple: [Hunder, hasCamelSpeciesUsedForSafaris, Bactrian camel]
-
A.
hasCamelSpecies
chosen
Indicates that one entity is a camel and the other specifies the biological species to which that camel belongs.
-
B.
hasWildlifeUse
Indicates that something is used by or provides a functional role for wildlife, such as habitat, food, shelter, or other ecological benefits.
-
C.
hasTypeOfWildlife
Indicates that an entity contains, supports, or is associated with a particular category or kind of wildlife.
-
D.
hasWildlifeObservation
Indicates that a wildlife observation event or record is associated with a particular entity (such as a location, time, or observer).
-
E.
hasWildlifeCharacteristic
Indicates that an entity possesses a particular trait, feature, or quality related to wildlife.
- F. None of above.
Provenance (4 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4117f3409c8190952967c5ef4892ef |
completed | June 28, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
Created at: May 3, 2026, 4:20 p.m.