Triple
T35834177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daeron I Targaryen |
E1035882
|
entity |
| Predicate | methodOfConquest |
P113615
|
FINISHED |
| Object | invasion by land and sea |
—
|
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: invasion by land and sea | Statement: [Daeron I Targaryen, methodOfConquest, invasion by land and sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfConquest Context triple: [Daeron I Targaryen, methodOfConquest, invasion by land and sea]
-
A.
methodOfInvasion
chosen
Indicates the specific way or technique by which an invasion is carried out.
-
B.
typeOfConquest
Indicates the specific manner or category of conquest by which one entity gains control over or dominance of another.
-
C.
realmConqueredBy
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
D.
conqueredThroughGeneral
Indicates that one entity achieved conquest or control over another entity by means of a specific general who led or directed the successful military action.
-
E.
conquestCampaign
Indicates a military or strategic campaign undertaken with the goal of conquering and taking control of a target entity or territory.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.