Triple
T37651960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opele chain |
E937197
|
entity |
| Predicate | methodOfUse |
P55465
|
FINISHED |
| Object | cast onto a divination tray or mat |
—
|
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: cast onto a divination tray or mat | Statement: [Opele chain, methodOfUse, cast onto a divination tray or mat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfUse Context triple: [Opele chain, methodOfUse, cast onto a divination tray or mat]
-
A.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
B.
isIntendedForUseBy
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
-
C.
partOfUse
Indicates that something functions as a component or constituent within the use or application of something else.
-
D.
usesMethods
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
-
E.
usedInMethod
chosen
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.