Triple
T26489511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nam-ku |
E669116
|
entity |
| Predicate | romanizationStandardIntroduced |
P67808
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [Nam-ku, romanizationStandardIntroduced, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanizationStandardIntroduced Context triple: [Nam-ku, romanizationStandardIntroduced, 1930s]
-
A.
romanizationStandardReplacedBy
Indicates that one system or convention for romanization has been superseded and replaced by another romanization standard.
-
B.
hasRomanizationStandard
Indicates that an entity’s romanized form follows a specified romanization standard or system.
-
C.
romanizationBegan
chosen
Indicates that the process of converting text from one writing system into its representation using the Roman (Latin) alphabet was initiated.
-
D.
romanizationType
Indicates the specific system or method used to convert text from one writing system into its Roman (Latin) alphabet representation.
-
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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 1:02 a.m.