Triple
T1248938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomahawk axe |
E26829
|
entity |
| Predicate | handleShape |
P25788
|
FINISHED |
| Object | straight |
—
|
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: straight | Statement: [Tomahawk axe, handleShape, straight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handleShape Context triple: [Tomahawk axe, handleShape, straight]
-
A.
baseShape
Indicates that one entity serves as the fundamental or underlying shape or form upon which another entity is defined, derived, or constructed.
-
B.
coreShape
Indicates that one entity serves as the primary or central shape or geometric form of another entity.
-
C.
seeksToShape
Indicates an entity’s intention or effort to influence, mold, or determine the form, direction, or outcome of another entity or situation.
-
D.
leafShape
Indicates the characteristic form or outline of a leaf that an entity possesses or exhibits.
-
E.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
- 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_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. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:47 p.m.