Triple
T17629962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teräs Käsi |
E429947
|
entity |
| Predicate | notableTechniqueType |
P22224
|
FINISHED |
| Object | strikes |
—
|
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: strikes | Statement: [Teräs Käsi, notableTechniqueType, strikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTechniqueType Context triple: [Teräs Käsi, notableTechniqueType, strikes]
-
A.
notableInstrumentTechnique
Indicates that an entity is particularly recognized for using, developing, or being associated with a specific musical instrument technique.
-
B.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
C.
notableTechnicalFeature
Indicates that an entity possesses a significant or distinguishing technical characteristic or capability.
-
D.
notableManeuver
chosen
Indicates that an entity is recognized for performing a specific maneuver, action, or tactical move that is considered notable or significant.
-
E.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dc01b1c819099e3329cfb8cb77f |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.