Triple
T21985039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hangul Syllables |
E542934
|
entity |
| Predicate | hasContiguousRange |
P88809
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hangul Syllables, hasContiguousRange, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContiguousRange Context triple: [Hangul Syllables, hasContiguousRange, true]
-
A.
hasContinuousSequence
chosen
Indicates that there exists an unbroken, ordered sequence or range connecting the related entities without gaps.
-
B.
isContiguousState
Indicates that a state shares a continuous land border with the main body of the country, without being separated by foreign territory or significant bodies of water.
-
C.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
isNonContiguous
Indicates that the related elements are separated by one or more gaps and do not form a single continuous sequence or region.
-
E.
includesRange
Indicates that one entity’s span, interval, or range fully contains or covers the span, interval, or range of another entity.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12708cdcc81909511d9f81bd8f20e |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:04 p.m.