Triple
T27474278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bǎojī |
E693410
|
entity |
| Predicate | provinceOfEntityRomanized |
P40220
|
FINISHED |
| Object | Shaanxi |
—
|
NE NERFINISHED |
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: Shaanxi | Statement: [Bǎojī, provinceOfEntityRomanized, Shaanxi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceOfEntityRomanized Context triple: [Bǎojī, provinceOfEntityRomanized, Shaanxi]
-
A.
provinceOf
Indicates that one administrative region functions as a province belonging to or governed by a larger territorial or political entity.
-
B.
isProvinceOf
chosen
Indicates that one region holds the administrative status of a province within, and is governed as a subnational division of, another political entity.
-
C.
prefectureOfHeadquarters
Indicates the administrative prefecture in which an organization's headquarters is located.
-
D.
hasProvinceName
Indicates that an entity (such as a province or region) bears or is associated with a specific province name.
-
E.
recognizedAsProvinceBy
Indicates that an entity is officially acknowledged or designated as a province by another specified authority or entity.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 27, 2026, 12:56 p.m.