Triple
T9670578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head Crusher |
E234014
|
entity |
| Predicate | characteristicAction |
P662
|
FINISHED |
| Object | mimes crushing people’s heads from a distance using his fingers |
—
|
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: mimes crushing people’s heads from a distance using his fingers | Statement: [Head Crusher, characteristicAction, mimes crushing people’s heads from a distance using his fingers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicAction Context triple: [Head Crusher, characteristicAction, mimes crushing people’s heads from a distance using his fingers]
-
A.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
C.
managementCharacteristic
Indicates a defining quality, style, or attribute associated with how something is managed or administered.
-
D.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
E.
projectCharacteristics
Indicates the defining features, qualities, or attributes that characterize a particular project.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3ec17081908c2da74a1d1f49da |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.