Triple
T34893840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blida |
E1006372
|
entity |
| Predicate | nearMountainResort |
P1981
|
FINISHED |
| Object | Chréa |
—
|
NE NERFINISHED |
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: Chréa | Statement: [Blida, nearMountainResort, Chréa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearMountainResort Context triple: [Blida, nearMountainResort, Chréa]
-
A.
mountainAccess
Indicates that an entity has the ability, right, or means to reach, enter, or utilize a mountain or mountainous area.
-
B.
hasSkiResortNearby
chosen
Indicates that one location is situated close enough to another location that it can be considered to have a ski resort in its vicinity.
-
C.
isAlpineResort
Indicates that the subject is a resort located in, or characteristic of, an alpine (mountainous) region.
-
D.
nearbySummit
Indicates that one summit is located close to another summit in geographic space.
-
E.
hasMountainPassNearby
Indicates that a mountain pass is located in close proximity to the referenced place or feature.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.