Triple
T23881322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 辛丑条约 |
E600207
|
entity |
| Predicate | 军事条款 |
P17742
|
FINISHED |
| Object | 允许列强在北京至山海关铁路沿线驻军 |
—
|
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: 允许列强在北京至山海关铁路沿线驻军 | Statement: [辛丑条约, 军事条款, 允许列强在北京至山海关铁路沿线驻军]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 军事条款 Context triple: [辛丑条约, 军事条款, 允许列强在北京至山海关铁路沿线驻军]
-
A.
militaryDoctrine
Indicates that one entity embodies, follows, or defines the strategic military principles, tactics, and operational guidelines used by another entity.
-
B.
militaryDomain
chosen
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
C.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
D.
militaryContext
Indicates that the relationship or action occurs within a military setting, framework, or operational environment.
-
E.
militaryLanguage
Indicates that the communication or expression is conveyed using military-specific terminology, style, or jargon.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cc05e4d48190864fc47bdffa4ca9 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:24 p.m.