Triple
T6248183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanja |
E139773
|
entity |
| Predicate | historicallyDominantBefore |
P5897
|
FINISHED |
| Object | Hangul adoption |
—
|
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: Hangul adoption | Statement: [Hanja, historicallyDominantBefore, Hangul adoption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyDominantBefore Context triple: [Hanja, historicallyDominantBefore, Hangul adoption]
-
A.
historicallyDominantIn
chosen
Indicates that one entity has held a position of prevailing power, influence, or control over another entity or within a particular domain during a past historical period.
-
B.
historicallyDominatedBy
Indicates that one entity has exercised controlling power or authority over another entity during a past historical period.
-
C.
dominatesSince
Indicates that one entity has maintained a position of dominance or control over another entity continuously from a specified starting time onward.
-
D.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
E.
historicallyConsidered
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0633a9a048190856d5247d3b28a2e |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.