Triple
T28880852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asukayama Park |
E732411
|
entity |
| Predicate | hasHillElevationType |
P50562
|
FINISHED |
| Object | low hill |
—
|
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: low hill | Statement: [Asukayama Park, hasHillElevationType, low hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHillElevationType Context triple: [Asukayama Park, hasHillElevationType, low hill]
-
A.
containsHill
Indicates that one entity geographically includes or encompasses a hill within its area or boundaries.
-
B.
isHill
Indicates that the subject entity is classified as a hill, i.e., a naturally raised area of land lower and less steep than a mountain.
-
C.
hasHillSize
Indicates that something possesses or is characterized by a particular hill size.
-
D.
hasElevationFeature
chosen
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
E.
hasApproximateNumberOfHills
Indicates that an entity is associated with an estimated or imprecise count of hills rather than an exact number.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 28, 2026, 7:44 a.m.