Triple
T34996500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lào Cai |
E1009544
|
entity |
| Predicate | statusOfCityDuringBattle |
P200087
|
FINISHED |
| Object | Lào Cai was a strategic border city |
—
|
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ào Cai was a strategic border city | Statement: [Battle of Lào Cai, statusOfCityDuringBattle, Lào Cai was a strategic border city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfCityDuringBattle Context triple: [Battle of Lào Cai, statusOfCityDuringBattle, Lào Cai was a strategic border city]
-
A.
cityStatusDuringSiege
Indicates the condition or status of a city specifically during the period in which it is under siege.
-
B.
statusOfCityBeforeBattle
Indicates the condition or situation a city was in immediately prior to a specific battle.
-
C.
foughtInCity
Indicates that an entity participated in a fight, battle, or conflict that took place within a specific city.
-
D.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
E.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related entity.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
| PDg | Predicate description generation | batch_69ff70ebec7481908d8a4124c8d531df |
completed | May 9, 2026, 5:37 p.m. |
Created at: May 3, 2026, 4:01 p.m.