Triple
T38405283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lộc Ninh |
E901008
|
entity |
| Predicate | temporarilyOverrunBy |
P191629
|
FINISHED |
| Object | North Vietnamese forces |
—
|
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: North Vietnamese forces | Statement: [Battle of Lộc Ninh, temporarilyOverrunBy, North Vietnamese forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarilyOverrunBy Context triple: [Battle of Lộc Ninh, temporarilyOverrunBy, North Vietnamese forces]
-
A.
eventuallyOverrunBy
Indicates that one entity is ultimately defeated, overwhelmed, or taken over by another entity or force after some passage of time.
-
B.
heldOver
Indicates that something has been continued, carried forward, or extended in effect or duration beyond its original or expected time.
-
C.
holdsOver
Indicates that a certain condition, state, or relationship remains valid or continues to apply across a specified period, context, or range.
-
D.
oversLimit
Indicates that an entity exceeds a specified limit, threshold, or allowed maximum.
-
E.
overtook
Indicates that one entity moved past and ahead of another that was previously in front, typically while both were in motion.
- F. None of above. chosen
Provenance (4 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_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:31 p.m.