Triple
T17463652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 居庸关 |
E425220
|
entity |
| Predicate | 历史时期沿用 |
P3656
|
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.
historicalPeriodOfUse
chosen
Indicates the time period during which something was in active use or commonly utilized.
-
B.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
-
C.
historicalDocumentationPeriod
Indicates the time span during which something is documented or recorded in historical sources.
-
D.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
E.
historicalPeriodOfCurrentForm
Indicates the historical period during which the entity’s current form, structure, or configuration came into existence or was established.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a5bba08190b61a21fa7538ed69 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.