Triple
T24891990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revised Romanization of Korean |
E623027
|
entity |
| Predicate | usesCapitalizationRules |
P151002
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Revised Romanization of Korean, usesCapitalizationRules, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCapitalizationRules Context triple: [Revised Romanization of Korean, usesCapitalizationRules, yes]
-
A.
usesCapitalization
Indicates that one entity applies specific capitalization (such as upper/lower case or title case) to another entity, typically a string or text element.
-
B.
capitalizationRequirement
Indicates that a specified text element must follow a particular capitalization rule or standard.
-
C.
preferredCapitalization
Indicates the specific way a term’s letters should be capitalized when it is written or displayed.
-
D.
capitalizationPolicy
chosen
Indicates the rules or conventions governing how letters are capitalized in a given context (e.g., text, names, or identifiers).
-
E.
capitalizationOccursWhen
Indicates that the event or condition specified is the point or circumstance under which capitalization (e.g., converting letters to uppercase or treating something as a capital asset) takes place.
- 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_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 5:26 a.m.