Triple
T33053902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costanza family holiday |
E845799
|
entity |
| Predicate | poleReasonForNoTinsel |
P165994
|
FINISHED |
| Object | tinsel is distracting |
—
|
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: tinsel is distracting | Statement: [Costanza family holiday, poleReasonForNoTinsel, tinsel is distracting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poleReasonForNoTinsel Context triple: [Costanza family holiday, poleReasonForNoTinsel, tinsel is distracting]
-
A.
notHeldReason
chosen
Indicates the reason or cause why a particular event, action, or state did not occur or was not carried out.
-
B.
noPointsFor
Indicates that an entity receives no credit, score, or reward as a result of a particular action, condition, or outcome.
-
C.
scrappingReason
Indicates the reason or justification for discarding or scrapping an item, asset, or entity from use.
-
D.
reasonForElimination
Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
-
E.
hasNotablePublicityReason
Indicates that an entity is associated with a specific reason or event that has led to notable public attention or publicity.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.