Triple
T9599365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parc de la Chute-Montmorency |
E231809
|
entity |
| Predicate | hasHighestPointAboveSeaLevel |
P89150
|
FINISHED |
| Object | about 83 metres |
—
|
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: about 83 metres | Statement: [Parc de la Chute-Montmorency, hasHighestPointAboveSeaLevel, about 83 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestPointAboveSeaLevel Context triple: [Parc de la Chute-Montmorency, hasHighestPointAboveSeaLevel, about 83 metres]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
countryOfHighestPoint
Indicates the country within whose territory a given location’s highest elevation point is found.
-
C.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
-
D.
territorialPeak
Indicates the highest geographical point located within the territory or jurisdiction of a given entity.
-
E.
emergedAboveSeaLevel
Indicates that something rose or became exposed above the surface of the sea from a previously submerged or lower position.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a3819608190b3c280f5e1845f85 |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:07 p.m.