Triple
T11659021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enderman |
E277076
|
entity |
| Predicate | calmableBy |
P73930
|
FINISHED |
| Object | wearing a carved pumpkin on head |
—
|
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: wearing a carved pumpkin on head | Statement: [Enderman, calmableBy, wearing a carved pumpkin on head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calmableBy Context triple: [Enderman, calmableBy, wearing a carved pumpkin on head]
-
A.
relievedBy
Indicates that one entity eases, reduces, or removes the burden, pain, stress, or responsibility experienced by another entity.
-
B.
cible
Indicates that one entity is the target or intended recipient of another entity’s action, focus, or effect.
-
C.
tamed
chosen
Indicates that one entity has brought another under control or domesticated it, reducing its wild or aggressive nature.
-
D.
stabilizedBy
Indicates that an entity’s state, structure, or behavior is made more steady, secure, or resistant to change through the influence or support of another entity.
-
E.
relief
Indicates a state or action in which distress, pain, or difficulty is reduced, eased, or removed for an 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.