Triple
T37336792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryojun |
E926912
|
entity |
| Predicate | currentPrefectureLevelCity |
P108882
|
FINISHED |
| Object | Dalian |
—
|
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: Dalian | Statement: [Ryojun, currentPrefectureLevelCity, Dalian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentPrefectureLevelCity Context triple: [Ryojun, currentPrefectureLevelCity, Dalian]
-
A.
isPrefecturalCityOf
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
B.
prefecture-levelCity
Indicates that one entity is a city that holds prefecture-level administrative status in relation to another entity (typically a higher-level region or governing structure).
-
C.
subprefectureCapital
Indicates that one entity serves as the administrative capital or seat of government for a given subprefecture.
-
D.
currentPrefectureOfVar
chosen
Indicates that a given entity is currently located in, or administratively belongs to, a specified prefecture.
-
E.
prefectureCapital
Indicates that a city serves as the administrative capital of a given prefecture.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:16 p.m.