Triple
T6328683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burseraceae |
E141920
|
entity |
| Predicate | hasUseIn |
P25490
|
FINISHED |
| Object | ritual and religious practices |
—
|
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: ritual and religious practices | Statement: [Burseraceae, hasUseIn, ritual and religious practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUseIn Context triple: [Burseraceae, hasUseIn, ritual and religious practices]
-
A.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
B.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
C.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
D.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
-
E.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651197908190a30e504e2442d40f |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.