Triple
T30173413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Shenyang |
E766985
|
entity |
| Predicate | regionSecured |
P175239
|
FINISHED |
| Object | Northeast China |
—
|
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: Northeast China | Statement: [Battle of Shenyang, regionSecured, Northeast China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionSecured Context triple: [Battle of Shenyang, regionSecured, Northeast China]
-
A.
sectorProtected
Indicates that a particular sector or area is safeguarded from harm, access, or exploitation by some form of protection or regulation.
-
B.
hasSecurityRegion
Indicates that an entity is associated with, governed by, or falls within a specific security region or security-related jurisdiction.
-
C.
securedTerritory
chosen
Indicates that an entity has successfully gained and established control over a specific territory, typically through force, negotiation, or strategic action.
-
D.
guardedRegion
Indicates that a region is protected or watched over by some guarding entity or mechanism.
-
E.
alsoSecured
Indicates that an entity has obtained or provided additional security or collateral in connection with an existing secured obligation or arrangement.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: April 29, 2026, 7:25 p.m.