Triple
T17529735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomahawk |
E426896
|
entity |
| Predicate | notableMarking |
P32310
|
FINISHED |
| Object | shark mouth nose art |
—
|
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: shark mouth nose art | Statement: [Tomahawk, notableMarking, shark mouth nose art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMarking Context triple: [Tomahawk, notableMarking, shark mouth nose art]
-
A.
distinctiveMarking
chosen
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
B.
markingFeature
Indicates a feature that serves as a distinguishing mark or identifier associated with an entity.
-
C.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
D.
notableBlock
Indicates that one entity is a block (e.g., text, code, or content segment) that is considered notable or significant in relation to another entity or context.
-
E.
marked
Indicates that one entity has been identified, labeled, or highlighted in some way by another entity.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45367d68c819097f300381322f11d |
completed | April 19, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.