Triple
T27894042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 白马寺 |
E705437
|
entity |
| Predicate | 所在国家行政区划 |
P35059
|
FINISHED |
| Object | 中华人民共和国 |
—
|
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: 中华人民共和国 | Statement: [白马寺, 所在国家行政区划, 中华人民共和国]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 所在国家行政区划 Context triple: [白马寺, 所在国家行政区划, 中华人民共和国]
-
A.
administrativeTerritoryType
Indicates the classification of an administrative area according to its level or type of territorial governance (e.g., city, county, province).
-
B.
administrativeTerritorialEntityOf
chosen
Indicates that one entity serves as the administrative territorial unit or jurisdiction to which another entity belongs or is governed by.
-
C.
isAdministrativeDivision
Indicates that one entity functions as an official administrative subdivision or jurisdiction within the governance structure of another entity.
-
D.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
E.
associatedAdministrativeRegion
Indicates that an entity is linked to, or falls under the jurisdiction of, a particular administrative region.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f639b7b29881909191f697802f043f |
completed | May 2, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:37 p.m.