Triple
T31664774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Korean won |
E808095
|
entity |
| Predicate | localNameRomanization |
P157446
|
FINISHED |
| Object | Daehanminguk won |
—
|
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: Daehanminguk won | Statement: [South Korean won, localNameRomanization, Daehanminguk won]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localNameRomanization Context triple: [South Korean won, localNameRomanization, Daehanminguk won]
-
A.
nameInLanguageRomanization
Indicates that an entity’s name is represented in the romanized (Latin-script) form of a particular language.
-
B.
exampleRomanization
chosen
Indicates that one entity is a romanized representation (in Latin script) of the other entity’s original text or name.
-
C.
hasRomanizationOf
Indicates that one entity is a romanized representation (written in the Latin alphabet) of the other entity’s original script form.
-
D.
romanizationFrom
Indicates that one entity is a romanized representation derived from the script or writing system of another entity.
-
E.
romanizationVariantOf
Indicates that one written form is a different romanized representation of the same underlying word or expression as another.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 30, 2026, 10:58 p.m.