Triple
T27123077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ichneumia albicauda |
E687051
|
entity |
| Predicate | avoidsHabitat |
P161871
|
FINISHED |
| Object | extreme desert |
—
|
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: extreme desert | Statement: [Ichneumia albicauda, avoidsHabitat, extreme desert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avoidsHabitat Context triple: [Ichneumia albicauda, avoidsHabitat, extreme desert]
-
A.
avoidsHabitat
chosen
Indicates that an entity deliberately does not occupy, use, or enter a particular habitat or environmental area.
-
B.
seeksToAvoid
Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
-
C.
preferredHabitat
Indicates the type of environment or habitat in which an entity most commonly lives or thrives.
-
D.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
E.
avoidedFor
Indicates that one entity is deliberately not used, chosen, or engaged with because of the presence, influence, or characteristics 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f624454be48190908449be1be4d1a4 |
completed | May 2, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9 a.m.