Triple
T3010113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christmas pyramids |
E82195
|
entity |
| Predicate | typicalScene |
P4566
|
FINISHED |
| Object | Nativity scene |
—
|
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: Nativity scene | Statement: [Christmas pyramids, typicalScene, Nativity scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalScene Context triple: [Christmas pyramids, typicalScene, Nativity scene]
-
A.
typicalPremise
Indicates that one situation or statement is a common or characteristic premise that typically leads to, supports, or underlies another situation or conclusion.
-
B.
typicalBackground
chosen
Indicates that an entity has a usual or commonly expected background, context, or setting associated with it.
-
C.
notableScene
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalGameLocation
Indicates the usual or characteristic place where a game is played or takes place.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4ccbf08190a7580c9e758804d0 |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.