Triple
T30591576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casa del Rey Moro |
E778670
|
entity |
| Predicate | waterMineLeadsTo |
P187386
|
FINISHED |
| Object | river level at bottom of Tajo Gorge |
—
|
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: river level at bottom of Tajo Gorge | Statement: [Casa del Rey Moro, waterMineLeadsTo, river level at bottom of Tajo Gorge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterMineLeadsTo Context triple: [Casa del Rey Moro, waterMineLeadsTo, river level at bottom of Tajo Gorge]
-
A.
waterMineAlsoKnownAs
Indicates that a water mine is referred to or known by an alternative name or alias.
-
B.
waterMineType
Indicates the type or category of a water-related mining operation associated with an entity.
-
C.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
D.
waterSourceDedicatedTo
Indicates that a particular water source is specifically allocated or reserved for a designated use, group, or purpose.
-
E.
waterSourceAfter
Indicates that one water source occurs, appears, or is accessed after another in time or sequence.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: April 29, 2026, 8:24 p.m.