Triple
T22106459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liaoyuan |
E546298
|
entity |
| Predicate | locatedInFormerManchuria |
P29444
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Liaoyuan, locatedInFormerManchuria, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFormerManchuria Context triple: [Liaoyuan, locatedInFormerManchuria, true]
-
A.
roleInManchuria
Indicates that an entity holds or held a specific role, position, or function in the context of Manchuria.
-
B.
locatedInFormerAdministrativeTerritory
chosen
Indicates that an entity is situated within the boundaries of an administrative territory that no longer exists or has been reorganized.
-
C.
locatedInAutonomousRegion
Indicates that one entity is geographically or administratively situated within a self-governing or semi-independent regional territory.
-
D.
locatedInAsia
Indicates that the subject entity is geographically situated within the continent of Asia.
-
E.
locatedInRegionOfRussia
Indicates that one entity is geographically situated within a specified region of Russia.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12919dd388190b8ca08e2464cb0b8 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.