Triple
T14485012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beric Dondarrion |
E359203
|
entity |
| Predicate | numberOfResurrections |
P94122
|
FINISHED |
| Object | multiple |
—
|
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: multiple | Statement: [Beric Dondarrion, numberOfResurrections, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfResurrections Context triple: [Beric Dondarrion, numberOfResurrections, multiple]
-
A.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
B.
isFrequentlyRevived
chosen
Indicates that an entity is brought back, restored, or reintroduced many times over a period.
-
C.
periodOfRevival
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
-
D.
revivesSpiritOf
Indicates restoring or reawakening the emotional, cultural, or motivational essence associated with someone or something.
-
E.
revivedAs
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924d7f4c8190b1f62b5ffe1ff649 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.