Triple
T6774631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 66th Regiment, People's Army of Vietnam |
E155124
|
entity |
| Predicate | engagementDate_BattleOfIaDrang |
P12233
|
FINISHED |
| Object | November 1965 |
—
|
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: November 1965 | Statement: [66th Regiment, People's Army of Vietnam, engagementDate_BattleOfIaDrang, November 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementDate_BattleOfIaDrang Context triple: [66th Regiment, People's Army of Vietnam, engagementDate_BattleOfIaDrang, November 1965]
-
A.
timeBeforeFallOfSaigon
Indicates that the referenced time point occurs chronologically before the fall of Saigon.
-
B.
placeOfMainEngagement
Indicates the primary location where an entity carries out its main activities, operations, or engagements.
-
C.
battleOfPhilippineSeaDate
Indicates the calendar date on which the Battle of the Philippine Sea took place.
-
D.
battleOccurredOn
chosen
Indicates that a specific battle took place at or on a particular location or date.
-
E.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d24ddaf08190baffbff991eeb458 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:13 p.m.