Triple
T30936492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wa State |
E788136
|
entity |
| Predicate | hasDeFactoBorderControl |
P145331
|
FINISHED |
| Object | with China |
—
|
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: with China | Statement: [Wa State, hasDeFactoBorderControl, with China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeFactoBorderControl Context triple: [Wa State, hasDeFactoBorderControl, with China]
-
A.
hasBorderControlBy
chosen
Indicates that the border of one entity is monitored, regulated, or managed by another entity.
-
B.
hasBorderControlAuthority
Indicates that an entity possesses the official power or responsibility to regulate and enforce controls at a border.
-
C.
hasBorderControlFacility
Indicates that one location possesses an official facility responsible for managing and controlling border crossings to or from another location.
-
D.
hasBorderControlIssues
Indicates that there are problems, weaknesses, or irregularities in the enforcement or management of border controls between entities.
-
E.
hasBorderControlHistory
Indicates that there is a documented history of actions, policies, or events related to border control involving the associated 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 29, 2026, 8:52 p.m.