Triple
T4124701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pinyon jay |
E92695
|
entity |
| Predicate | caches |
P54421
|
FINISHED |
| Object | pinyon pine seeds |
—
|
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: pinyon pine seeds | Statement: [pinyon jay, caches, pinyon pine seeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caches Context triple: [pinyon jay, caches, pinyon pine seeds]
-
A.
captures
Indicates that one entity seizes, traps, or takes control of another entity, often preventing its escape or freedom.
-
B.
caps
Indicates that one entity serves as the capital city or administrative center of another entity, such as a country, state, or region.
-
C.
catches
Indicates that one entity successfully seizes, intercepts, or takes hold of another entity, often stopping its motion or preventing its escape.
-
D.
conserves
Indicates that an entity protects, preserves, or maintains another entity or resource in its existing state, preventing loss, damage, or depletion.
-
E.
reserves
Indicates that an entity has arranged in advance to hold or secure something for future use or access.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af0245adbc81908b89a40850047975 |
completed | March 9, 2026, 5:24 p.m. |
Created at: March 9, 2026, 3:41 p.m.