Triple
T23406134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanji |
E559937
|
entity |
| Predicate | autonomousPrefectureType |
P152139
|
FINISHED |
| Object | Korean autonomous prefecture |
—
|
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: Korean autonomous prefecture | Statement: [Yanji, autonomousPrefectureType, Korean autonomous prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonomousPrefectureType Context triple: [Yanji, autonomousPrefectureType, Korean autonomous prefecture]
-
A.
prefectureOfHeadquarters
Indicates the administrative prefecture in which an organization's headquarters is located.
-
B.
isPrefecture
Indicates that one entity functions as an administrative prefecture governing or representing the other entity.
-
C.
都道府県
Indicates a relationship where an entity is a Japanese prefecture or belongs to/pertains to a specific Japanese prefecture.
-
D.
isPrefecturalCityOf
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
E.
accessPrefecture
Indicates that an entity has access to, or is associated with accessing, a specific prefecture.
- F. None of above. chosen
Provenance (4 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4e364548190b98dc09240fba58e |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:38 p.m.