Triple
T26094201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Debal |
E658213
|
entity |
| Predicate | portCityCaptured |
P8502
|
FINISHED |
| Object | Debal |
—
|
NE NERFINISHED |
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: Debal | Statement: [Battle of Debal, portCityCaptured, Debal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portCityCaptured Context triple: [Battle of Debal, portCityCaptured, Debal]
-
A.
capitalOfProvinceCaptured
Indicates that a particular force or entity has taken control of the capital city of a specified province.
-
B.
fortificationCaptured
Indicates that control of a defensive structure or fortified position has been taken from one party by another.
-
C.
conqueredCity
chosen
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
-
D.
dateOfCityCapture
Indicates the specific date on which a city was taken or captured, typically in a military or political context.
-
E.
countryWhoseCityWasCaptured
Indicates that a country is one whose city was captured, typically in a military or conflict-related context.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f607347dd881909aa749e2f3527adb |
completed | May 2, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:49 p.m.