Triple
T14237409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chūgoku Mountains |
E352919
|
entity |
| Predicate | isMajorRangeIn |
P81006
|
FINISHED |
| Object | western Honshu |
—
|
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: western Honshu | Statement: [Chūgoku Mountains, isMajorRangeIn, western Honshu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorRangeIn Context triple: [Chūgoku Mountains, isMajorRangeIn, western Honshu]
-
A.
hasMajorRange
Indicates that one entity encompasses or defines the primary or most extensive range or scope associated with another entity.
-
B.
majorRangeIncludes
Indicates that a major range (such as a primary geographic or categorical span) encompasses or contains another specified range.
-
C.
isMajorSeeWithin
chosen
Indicates that one entity is the primary or most significant location or area encompassed within the boundaries of another entity.
-
D.
isMajorIndexOf
Indicates that one entity serves as the primary or major index reference for locating, organizing, or identifying another entity.
-
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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62422e28819089e7115052a28c96 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.