Triple
T33569730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长寿路 |
E859860
|
entity |
| Predicate | 所属国家ISO代码 |
P43867
|
FINISHED |
| Object | CN |
—
|
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: CN | Statement: [长寿路, 所属国家ISO代码, CN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 所属国家ISO代码 Context triple: [长寿路, 所属国家ISO代码, CN]
-
A.
parentISO3166Code
chosen
Indicates that one geographic or political entity is hierarchically contained within or derived from another, as represented by its parent ISO 3166 country or region code.
-
B.
hasISO3166-1NumericCode
Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
-
C.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
D.
denotesCountryWithISO3166-1Entry
Indicates that a country is associated with a specific ISO 3166-1 standard entry that formally codes and identifies it.
-
E.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f742f9788190be2d5890a46bfe8b |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.