Triple
T2095169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinmen |
E32763
|
entity |
| Predicate | borderStatus |
P3948
|
FINISHED |
| Object | frontline between ROC and PRC |
—
|
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: frontline between ROC and PRC | Statement: [Kinmen, borderStatus, frontline between ROC and PRC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderStatus Context triple: [Kinmen, borderStatus, frontline between ROC and PRC]
-
A.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
B.
borderRegime
chosen
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
C.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba99ddc48190bb2097b56efb7aca |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.