Triple
T33079688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiaojinmen |
E846472
|
entity |
| Predicate | borderConflictContext |
P3680
|
FINISHED |
| Object | Cross-Strait conflict |
—
|
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: Cross-Strait conflict | Statement: [Xiaojinmen, borderConflictContext, Cross-Strait conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderConflictContext Context triple: [Xiaojinmen, borderConflictContext, Cross-Strait conflict]
-
A.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
B.
conflictContext
chosen
Indicates the situational background or circumstances within which a conflict between entities occurs or is interpreted.
-
C.
loreConflict
Indicates that there is an inconsistency, contradiction, or incompatibility between pieces of lore or canonical information.
-
D.
conflictRegion
Indicates that the entities are located in or associated with a geographic area characterized by active or recent conflict, tension, or hostilities.
-
E.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: May 1, 2026, 1:25 a.m.