Triple
T2064154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodosian Walls |
E45857
|
entity |
| Predicate | partiallyBreachedIn |
P23714
|
FINISHED |
| Object | 1204 |
—
|
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: 1204 | Statement: [Theodosian Walls, partiallyBreachedIn, 1204]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyBreachedIn Context triple: [Theodosian Walls, partiallyBreachedIn, 1204]
-
A.
partiallyDestroyed
chosen
Indicates that an entity has been damaged or ruined to a significant extent but not completely destroyed.
-
B.
partlyProtectedBy
Indicates that an entity is only partially safeguarded or covered by a specified protective measure, not fully protected.
-
C.
partiallyRecapturedBy
Indicates that an entity that was previously captured or controlled has been regained only in part by another entity, not fully restored to its prior captured state.
-
D.
currentTerritoryPartlyIn
Indicates that a territory is currently located such that only a portion of it lies within another specified territory or area.
-
E.
damagedIn
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9d5147c8190a264fe42f0634cec |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.