Triple
T37664885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackstone |
E937798
|
entity |
| Predicate | canBeUsedToCraft |
P188346
|
FINISHED |
| Object | stone tools |
—
|
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: stone tools | Statement: [Blackstone, canBeUsedToCraft, stone tools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedToCraft Context triple: [Blackstone, canBeUsedToCraft, stone tools]
-
A.
craftable
chosen
Indicates that one entity can be created, assembled, or produced from other entities or resources, typically through a defined crafting process.
-
B.
cannotBeCrafted
Indicates that the item or entity cannot be created or produced through any crafting process or recipe.
-
C.
canBeObtainedFrom
Indicates that one entity is derivable, producible, or acquirable from another entity as a source or origin.
-
D.
isCraftProduct
Indicates that something is a product created through skilled manual craftsmanship, often in small-scale or artisanal production rather than mass manufacturing.
-
E.
hasCraft
Indicates a relationship where an entity possesses, operates, or is associated with a particular vehicle, vessel, or other craft.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
Created at: May 3, 2026, 4:18 p.m.