Triple
T38279522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bsharri, Lebanon |
E1022045
|
entity |
| Predicate | notableValleyNearby |
P19575
|
FINISHED |
| Object | Qadisha Valley (Holy Valley) |
E531932
|
NE 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: Qadisha Valley (Holy Valley) | Statement: [Bsharri, Lebanon, notableValleyNearby, Qadisha Valley (Holy Valley)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableValleyNearby Context triple: [Bsharri, Lebanon, notableValleyNearby, Qadisha Valley (Holy Valley)]
-
A.
notableValley
Indicates that a valley is recognized as significant or noteworthy, for example due to its geography, history, or cultural importance.
-
B.
notableNearbySite
chosen
Indicates that one entity is a significant or noteworthy site located close to another entity.
-
C.
nearbySummit
Indicates that one summit is located close to another summit in geographic space.
-
D.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
E.
nearbyMountainRegion
Indicates that one location is situated close to or within the surrounding area of a mountainous region.
- F. None of above.
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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41c27012c88190bfe5f333d3af040a |
completed | June 29, 2026, 12:55 a.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.