Triple
T15818160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | red-cockaded woodpecker |
E383531
|
entity |
| Predicate | cavityUse |
P120192
|
FINISHED |
| Object | creates resin wells around cavity entrances |
—
|
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: creates resin wells around cavity entrances | Statement: [red-cockaded woodpecker, cavityUse, creates resin wells around cavity entrances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cavityUse Context triple: [red-cockaded woodpecker, cavityUse, creates resin wells around cavity entrances]
-
A.
toothUsedBy
Indicates that a tooth is utilized or employed by a particular entity (such as an organism or tool) for some function or action.
-
B.
cavesUsedFor
Indicates that certain caves are utilized for a particular purpose, activity, or function by an entity.
-
C.
partOfUse
Indicates that something functions as a component or constituent within the use or application of something else.
-
D.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
E.
toothUsedToDestroy
Indicates that a tooth is employed as the means or tool to break, damage, or destroy something.
- F. None of above. chosen
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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a4332c8190bc525e06d6f3a6b4 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e00e48d49c819081afccb02f9cf18b |
completed | April 15, 2026, 10:16 p.m. |
Created at: April 10, 2026, 4:49 a.m.