Triple
T21942141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngo Quyen |
E541847
|
entity |
| Predicate | resultOfBattleOfBachDang |
P19109
|
FINISHED |
| Object | destruction of Southern Han fleet |
—
|
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: destruction of Southern Han fleet | Statement: [Ngo Quyen, resultOfBattleOfBachDang, destruction of Southern Han fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfBattleOfBachDang Context triple: [Ngo Quyen, resultOfBattleOfBachDang, destruction of Southern Han fleet]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
resultOfMilitaryCampaign
Indicates that one event, condition, or outcome occurs as a direct consequence of a specified military campaign.
-
C.
resultOfSiege
Indicates that one entity is the outcome or consequence produced by a siege conducted against another entity.
-
D.
opponentInBattleOfIaDrang
Indicates that one entity served as an opposing force to another in the Battle of Ia Drang.
-
E.
isFinalLandBattleOf
Indicates that one battle is the last major land engagement within a specified war, campaign, 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1242345dc8190aa6ddf61cf864e2d |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:56 p.m.