Triple
T1248956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomahawk axe |
E26829
|
entity |
| Predicate | canFeature |
P203
|
FINISHED |
| Object | pipe bowl (in pipe tomahawks) |
—
|
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: pipe bowl (in pipe tomahawks) | Statement: [Tomahawk axe, canFeature, pipe bowl (in pipe tomahawks)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canFeature Context triple: [Tomahawk axe, canFeature, pipe bowl (in pipe tomahawks)]
-
A.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
B.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
-
C.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf83b32c81908648e5748b897247 |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.