Triple
T15861346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shireen Baratheon |
E384592
|
entity |
| Predicate | survivedDisease |
P120800
|
FINISHED |
| Object | greyscale |
—
|
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: greyscale | Statement: [Shireen Baratheon, survivedDisease, greyscale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivedDisease Context triple: [Shireen Baratheon, survivedDisease, greyscale]
-
A.
survivalAttributedTo
Indicates that an entity’s continued existence or survival is credited to, or causally linked with, another entity or factor.
-
B.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
C.
curedWith
Indicates that one entity is treated or healed by using another entity as the remedy or therapeutic method.
-
D.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
-
E.
survivesWith
Indicates that one entity continues to live, endure, or remain viable in the presence, context, or company of another entity.
- F. None of above. chosen
Provenance (4 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.