Triple
T14781152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle at the Wall |
E347390
|
entity |
| Predicate | attackingDirection |
P49414
|
FINISHED |
| Object | from the north of the Wall |
—
|
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: from the north of the Wall | Statement: [Battle at the Wall, attackingDirection, from the north of the Wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackingDirection Context triple: [Battle at the Wall, attackingDirection, from the north of the Wall]
-
A.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
-
B.
primaryAdversaryDirection
chosen
Indicates the direction from an entity toward its main or most significant adversary.
-
C.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
D.
attackerSide
Indicates which party or faction is responsible for carrying out an attack in a conflict or violent incident.
-
E.
mainAttacker
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another entity.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deca9de3f48190b7706925e2947cf5 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.