Triple
T23454716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanbian |
E567885
|
entity |
| Predicate | hasEthnicEducation |
P152348
|
FINISHED |
| Object | Korean-language schools |
—
|
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-language schools | Statement: [Yanbian, hasEthnicEducation, Korean-language schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicEducation Context triple: [Yanbian, hasEthnicEducation, Korean-language schools]
-
A.
hasMajorEthnicMinority
Indicates that an entity includes a significant ethnic minority group within its overall population or composition.
-
B.
hasAlumniEthnicity
Indicates that there exists an alumni relationship where the alumni are associated with a specified ethnicity.
-
C.
hasEthnicScope
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
-
D.
hasEthnicDivision
Indicates that a group, region, or entity is characterized by internal divisions or distinctions based on ethnicity.
-
E.
hasEthnicTarget
Indicates that an action, statement, or event is directed toward or targets a specific ethnic group.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a695fed08190bfa160e69200546d |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:53 p.m.