Triple
T1716266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dancer |
E37295
|
entity |
| Predicate | hasNotableLineContext |
P3574
|
FINISHED |
| Object | “Now, Dasher! now, Dancer! now, Prancer and Vixen!” |
—
|
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: “Now, Dasher! now, Dancer! now, Prancer and Vixen!” | Statement: [Dancer, hasNotableLineContext, “Now, Dasher! now, Dancer! now, Prancer and Vixen!”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLineContext Context triple: [Dancer, hasNotableLineContext, “Now, Dasher! now, Dancer! now, Prancer and Vixen!”]
-
A.
hasNotableSegment
chosen
Indicates that an entity includes or contains a specific segment, part, or portion that is considered notable or significant in some way.
-
B.
notableRuleContext
Indicates that a rule, regulation, or guideline is being applied or interpreted within a particularly important or noteworthy contextual situation.
-
C.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion to, another entity.
-
D.
hasNotableResponse
Indicates that an entity has received a significant, noteworthy, or widely recognized reaction or feedback in response to it.
-
E.
hasNotableReaderBase
Indicates that an entity is associated with a large, prominent, or otherwise noteworthy group of readers or audience.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.