Triple
T768498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Single-leaf pinyon |
E16226
|
entity |
| Predicate | humanUse |
P8225
|
FINISHED |
| Object | source of edible nuts |
—
|
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: source of edible nuts | Statement: [Single-leaf pinyon, humanUse, source of edible nuts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanUse Context triple: [Single-leaf pinyon, humanUse, source of edible nuts]
-
A.
hasHumanUse
chosen
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
B.
plannedUseOf
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
C.
humanImpact
Indicates the effect or influence that human activities have on another entity, system, or environment.
-
D.
economicUse
Indicates that one entity utilizes another for economic purposes, such as production, trade, revenue generation, or cost-saving activities.
-
E.
politicalUse
Indicates that something is used for political purposes, such as influencing, supporting, or opposing political actors, policies, or processes.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a765ba688190ab328bb159583077 |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a5074c788190a74fc20ad24e2d26 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.