Triple
T35589190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Draa River |
E1028444
|
entity |
| Predicate | hasValleyKnownFor |
P56913
|
FINISHED |
| Object | date palm groves |
—
|
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: date palm groves | Statement: [Draa River, hasValleyKnownFor, date palm groves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasValleyKnownFor Context triple: [Draa River, hasValleyKnownFor, date palm groves]
-
A.
valleyKnownFor
chosen
Indicates that a particular valley is widely recognized or notable for a specific feature, product, activity, or characteristic.
-
B.
isInTownKnownFor
Indicates that one entity is located in a town that is notable or distinguished for the other entity.
-
C.
hasValley
Indicates that one entity contains, features, or is characterized by the presence of a valley associated with the other entity.
-
D.
hasHeadOfValleyNear
Indicates that the head (uppermost part) of a valley is located near a specified reference feature or entity.
-
E.
hasValleyCharacteristic
Indicates that something possesses a feature, quality, or attribute that is characteristic of a valley.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.