Triple
T12301347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laoting County, Hebei, Qing Empire |
E293229
|
entity |
| Predicate | timeLocatedInQingEmpire |
P89009
|
FINISHED |
| Object | before 1912 |
—
|
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: before 1912 | Statement: [Laoting County, Hebei, Qing Empire, timeLocatedInQingEmpire, before 1912]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeLocatedInQingEmpire Context triple: [Laoting County, Hebei, Qing Empire, timeLocatedInQingEmpire, before 1912]
-
A.
timeLocatedIn
chosen
Indicates that an event, state, or entity occurs, exists, or is valid within a specified time or temporal interval.
-
B.
functionInQingDynasty
Indicates that an entity held a particular official role, position, or function during the Qing Dynasty.
-
C.
compiledUnderDynasty
Indicates that a work or document was compiled during the reign or period of a specific dynasty.
-
D.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
E.
regionOfDynasty
Indicates the geographic region or area in which a given dynasty held power or was primarily based.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.