Triple
T168644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koreatown (Manhattan) |
E3070
|
entity |
| Predicate | ethnicFocus |
P1968
|
FINISHED |
| Object | Korean American |
—
|
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 American | Statement: [Koreatown (Manhattan), ethnicFocus, Korean American]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicFocus Context triple: [Koreatown (Manhattan), ethnicFocus, Korean American]
-
A.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
B.
culturalRegion
chosen
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
C.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
D.
recognizedAsMinorityIn
Indicates that an entity is officially acknowledged or classified as belonging to a minority group within a specified context or jurisdiction.
-
E.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a258b6f4f88190b1264bbbeb19a29e |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25665f5b8819096ca3e084faf976e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.