Triple
T3145266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HS100 (normal hill) |
E65747
|
entity |
| Predicate | hasLargerCompanionHill |
P46346
|
FINISHED |
| Object | HS140 (large 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: HS140 (large hill) | Statement: [HS100 (normal hill), hasLargerCompanionHill, HS140 (large hill)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLargerCompanionHill Context triple: [HS100 (normal hill), hasLargerCompanionHill, HS140 (large hill)]
-
A.
hasHillSize
Indicates that something possesses or is characterized by a particular hill size.
-
B.
hasSummitOnSideOf
Indicates that the summit or highest point of one geographic feature is located on the side of another feature.
-
C.
isSecondHighestPeakIn
Indicates that one entity is the mountain or peak with the second greatest elevation within the geographic or contextual set defined by the other entity.
-
D.
containsHill
Indicates that one entity geographically includes or encompasses a hill within its area or boundaries.
-
E.
hasMountain
Indicates that a location or region possesses or contains at least one mountain.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada59797788190a8d71262888c5df0 |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:05 p.m.