Triple
T35118291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andals |
E1014101
|
entity |
| Predicate | supplantedCulture |
P51283
|
FINISHED |
| Object | First Men in southern Westeros |
—
|
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: First Men in southern Westeros | Statement: [Andals, supplantedCulture, First Men in southern Westeros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supplantedCulture Context triple: [Andals, supplantedCulture, First Men in southern Westeros]
-
A.
replacedCulture
chosen
Indicates that one culture has been supplanted or taken the place of another culture.
-
B.
dominantCulture
Indicates that one culture holds prevailing power, influence, or normative status over others within a given social context.
-
C.
successorCulture
Indicates that one culture directly follows and continues or replaces another culture in time, inheriting or building upon its traditions or characteristics.
-
D.
usedCulture
Indicates that one entity employed, applied, or drew upon the cultural practices, norms, or artifacts associated with another entity.
-
E.
predecessorCulture
Indicates that one culture historically preceded and contributed to the development of another culture.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.