Triple
T5139971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holly |
E115919
|
entity |
| Predicate | yearOfCharacterIntroduction |
P3297
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [Holly, yearOfCharacterIntroduction, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfCharacterIntroduction Context triple: [Holly, yearOfCharacterIntroduction, 1952]
-
A.
introducedByCharacter
Indicates that one character is responsible for presenting, bringing into the story, or otherwise causing another entity to be first revealed or made known.
-
B.
introducedByCharacters
Indicates that something (such as an idea, object, or event) is brought into the narrative or context by specific characters.
-
C.
introducedInYear
chosen
Indicates the year in which something was first introduced, launched, or made available.
-
D.
notableCharacterCreated
Indicates that one entity is a notable or significant character that was created by another entity.
-
E.
introducedDuring
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
- 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_69bd44459a988190a772a5c2ec6a1965 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78d7f4d081908d59adcd86f52f1d |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77ae2f10819098bb8939106e1281 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:43 p.m.