Triple
T17311914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Trenzalore |
E420319
|
entity |
| Predicate | hasObjectiveOfDefenders |
P56145
|
FINISHED |
| Object | protect Trenzalore |
—
|
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: protect Trenzalore | Statement: [Siege of Trenzalore, hasObjectiveOfDefenders, protect Trenzalore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObjectiveOfDefenders Context triple: [Siege of Trenzalore, hasObjectiveOfDefenders, protect Trenzalore]
-
A.
objectiveOfDefenders
chosen
Indicates that a particular goal, task, or purpose is assigned to or pursued by the defenders in a given context.
-
B.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
-
C.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
D.
objectiveOfAttackers
Indicates the target or goal that attackers aim to reach or affect through their attack.
-
E.
hasDefensivePositions
Indicates that an entity possesses or controls locations, structures, or arrangements specifically organized for defense against potential threats or attacks.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439993bac8190a72f6af529bd7cce |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.