Triple
T2912073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purim spiels |
E63703
|
entity |
| Predicate | characteristicallyFeature |
P662
|
FINISHED |
| Object | humor |
—
|
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: humor | Statement: [Purim spiels, characteristicallyFeature, humor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicallyFeature Context triple: [Purim spiels, characteristicallyFeature, humor]
-
A.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
C.
keyFeature
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
D.
charterFeature
Indicates that an entity (such as a service, product, or offering) includes or provides a specific feature as part of a charter or special arrangement.
-
E.
traditionCharacteristic
Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given tradition.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0eb77708190b745b887f3b9a618 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.