Triple
T37554303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obsidian Edged Blade |
E933657
|
entity |
| Predicate | isBindOnPickup |
P188282
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Obsidian Edged Blade, isBindOnPickup, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBindOnPickup Context triple: [Obsidian Edged Blade, isBindOnPickup, true]
-
A.
hasPickup
Indicates that one entity is assigned or associated with a specific pickup location, time, or arrangement for collection.
-
B.
usesPickupType
Indicates that one entity employs or operates a specific type of pickup in performing its function or action.
-
C.
isBindingIn
Indicates that one entity functions as a binding site or context in which another entity is bound or attached.
-
D.
isInitiallyBoundWith
Indicates that two or more entities are connected, associated, or constrained together at the starting point of a process, state, or interaction.
-
E.
bindingOn
Indicates that one party is legally or formally obligated to follow, accept, or be governed by a decision, rule, or agreement established by another.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.