Triple
T28590219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Manchuria |
E723618
|
entity |
| Predicate | preQingCoreArea |
P18596
|
FINISHED |
| Object | HomelandOfManchuPeople |
—
|
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: HomelandOfManchuPeople | Statement: [History of Manchuria, preQingCoreArea, HomelandOfManchuPeople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preQingCoreArea Context triple: [History of Manchuria, preQingCoreArea, HomelandOfManchuPeople]
-
A.
coreAreaOf
Indicates that one entity is the central, primary, or most important area or domain of focus for another entity.
-
B.
coreRegionOf
chosen
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
C.
protectedAreaCore
Indicates that an entity lies within the core, most strictly protected zone of a designated protected area.
-
D.
coreZoneArea
Indicates the area or spatial extent of a designated core zone within a larger region or system.
-
E.
plannedArea
Indicates that an area is designated or intended for a specific planned use or development.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:20 a.m.