Triple
T38405282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lộc Ninh |
E901008
|
entity |
| Predicate | townOverrun |
P38805
|
FINISHED |
| Object | Lộc Ninh |
—
|
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: Lộc Ninh | Statement: [Battle of Lộc Ninh, townOverrun, Lộc Ninh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: townOverrun Context triple: [Battle of Lộc Ninh, townOverrun, Lộc Ninh]
-
A.
citySacked
chosen
Indicates that a city has been violently attacked, looted, and destroyed or heavily damaged, typically as a result of military conquest.
-
B.
townStatus
Indicates the administrative or legal status of a settlement as a town (e.g., whether and how it is officially recognized or classified as a town).
-
C.
stationAttacked
Indicates that an attack has been carried out against a station, targeting it with hostile or destructive actions.
-
D.
cityAttackedBy
Indicates that a city is the target of an attack carried out by a specified agent or force.
-
E.
townDefendedBy
Indicates that a particular town is protected or guarded by a specified defending force or 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.