Triple
T8397412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarduri I |
E198087
|
entity |
| Predicate | conflictSphere |
P21190
|
FINISHED |
| Object | Northern frontier of Assyria |
—
|
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: Northern frontier of Assyria | Statement: [Sarduri I, conflictSphere, Northern frontier of Assyria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictSphere Context triple: [Sarduri I, conflictSphere, Northern frontier of Assyria]
-
A.
conflictRegion
chosen
Indicates that the entities are located in or associated with a geographic area characterized by active or recent conflict, tension, or hostilities.
-
B.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
C.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
D.
conflictForControlOf
Indicates a struggle or contest between parties to gain dominance, authority, or decision-making power over something.
-
E.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb818a8dc081908efd5d7f910322e7 |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:04 p.m.