Triple
T30790115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troy Sentinel |
E784068
|
entity |
| Predicate | hasPoemVersion |
P114956
|
FINISHED |
| Object | early printed version of "A Visit from St. Nicholas" |
—
|
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: early printed version of "A Visit from St. Nicholas" | Statement: [Troy Sentinel, hasPoemVersion, early printed version of "A Visit from St. Nicholas"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoemVersion Context triple: [Troy Sentinel, hasPoemVersion, early printed version of "A Visit from St. Nicholas"]
-
A.
hasPoemOrRhymeVersion
chosen
Indicates that one entity is a poem or rhyme version, adaptation, or variant of another entity.
-
B.
hasCanonicalPoem
Indicates that an entity is associated with a poem recognized as its standard or authoritative version.
-
C.
hasPoemSetIn
Indicates that a poem is set in or takes place within a particular location or setting.
-
D.
hasPoemType
Indicates that an entity (such as a poem or literary work) is associated with or classified by a specific type or category of poem.
-
E.
containsPoem
Indicates that one entity includes or holds a poem as part of its contents.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 29, 2026, 8:41 p.m.