Triple
T27282971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | white-tailed mongoose |
E688387
|
entity |
| Predicate | usesShelterOf |
P101706
|
FINISHED |
| Object | abandoned burrows |
—
|
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: abandoned burrows | Statement: [white-tailed mongoose, usesShelterOf, abandoned burrows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesShelterOf Context triple: [white-tailed mongoose, usesShelterOf, abandoned burrows]
-
A.
hasShelters
Indicates that one entity provides, contains, or is associated with one or more shelters for another entity or purpose.
-
B.
shelterType
Indicates the kind or category of shelter associated with an entity (e.g., tent, house, bunker).
-
C.
takenAsRefugeBy
chosen
Indicates that one entity is used or relied upon by another entity as a place or source of safety, protection, or refuge.
-
D.
relativeShelterFrom
Indicates that one entity provides shelter or protection for another entity relative to some reference condition, location, or alternative.
-
E.
hasNearbySanctuary
Indicates that one entity has a sanctuary or place of refuge located close to it in space or distance.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 11:09 a.m.