Triple
T24891987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revised Romanization of Korean |
E623027
|
entity |
| Predicate | usesApostrophes |
P64285
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Revised Romanization of Korean, usesApostrophes, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesApostrophes Context triple: [Revised Romanization of Korean, usesApostrophes, no]
-
A.
isWrittenWithApostrophe
chosen
Indicates that something (typically a word, phrase, or name) is written using an apostrophe character as part of its spelling or punctuation.
-
B.
usesWord
Indicates that one entity employs, contains, or makes use of a particular word in its expression, content, or communication.
-
C.
usesColloquialCharacters
Indicates that an expression, name, or text is written using informal, non-standard, or colloquial characters rather than formal or standard script.
-
D.
usesDiacritics
Indicates that the referenced text or linguistic element employs diacritical marks as part of its written form.
-
E.
usesHyphens
Indicates that one entity employs or contains hyphens in its form, representation, or notation.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:26 a.m.