Triple
T23911617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival des Templiers |
E601951
|
entity |
| Predicate | typeOfElevationProfile |
P6557
|
FINISHED |
| Object | hilly and mountainous |
—
|
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: hilly and mountainous | Statement: [Festival des Templiers, typeOfElevationProfile, hilly and mountainous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfElevationProfile Context triple: [Festival des Templiers, typeOfElevationProfile, hilly and mountainous]
-
A.
elevationType
chosen
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
B.
altitudeProfile
Indicates the variation of elevation or height along a path, route, or trajectory over distance or time.
-
C.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
D.
elevationGainFunction
Indicates a functional relationship that maps a path, route, or movement to the total amount of elevation gained along it.
-
E.
hasElevationRank
Indicates the relative ordering of an entity based on its elevation compared to others.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce95f4848190b98339d8a6c988ba |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:38 p.m.