Triple
T24197098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ural–Altaic hypothesis |
E599862
|
entity |
| Predicate | hasDisputedComponent |
P155145
|
FINISHED |
| Object | Korean language |
—
|
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: Korean language | Statement: [Ural–Altaic hypothesis, hasDisputedComponent, Korean language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisputedComponent Context triple: [Ural–Altaic hypothesis, hasDisputedComponent, Korean language]
-
A.
hasDisputedStatus
Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
-
B.
hasDisputedStatusWith
Indicates that there is a contested or unresolved status, claim, or standing between the related entities.
-
C.
hasDisputedSector
Indicates that there exists a sector or area whose ownership, control, or status between the related entities is contested or not mutually agreed upon.
-
D.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
E.
hasDisputedClause
Indicates that a particular clause within an agreement or document is subject to disagreement, challenge, or contention between involved parties.
- F. None of above. chosen
Provenance (4 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e24c103481908ea49dd8e77dee32 |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:36 p.m.