Triple
T17737678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Iwate |
E442764
|
entity |
| Predicate | hasSecondaryPeaks |
P48061
|
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: [Mount Iwate, hasSecondaryPeaks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryPeaks Context triple: [Mount Iwate, hasSecondaryPeaks, yes]
-
A.
hasSecondaryPeak
chosen
Indicates that an entity exhibits an additional, smaller peak or maximum beyond its primary peak in its profile or behavior.
-
B.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
C.
hasSecondaryBase
Indicates that an entity possesses or is associated with a secondary or additional base, distinct from its primary base.
-
D.
hasSecondaryCore
Indicates that an entity possesses an additional, subordinate core component alongside its primary core.
-
E.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47aca27448190943c75e723ceefcc |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:09 a.m.