Triple
T30620841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tormes basin |
E779439
|
entity |
| Predicate | includesSubrange |
P2889
|
FINISHED |
| Object | Sierra de Gredos |
—
|
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: Sierra de Gredos | Statement: [Tormes basin, includesSubrange, Sierra de Gredos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSubrange Context triple: [Tormes basin, includesSubrange, Sierra de Gredos]
-
A.
includesRange
Indicates that one entity’s span, interval, or range fully contains or covers the span, interval, or range of another entity.
-
B.
rangeIncludes
Indicates that the values or results associated with a property are expected to be of the specified type or types.
-
C.
partOfRange
Indicates that one entity is included within, or constitutes a segment of, the overall extent or span defined by another entity.
-
D.
climbedInSubrange
Indicates that one entity’s climbing action occurred within a specified subrange of another entity’s climb or of a defined interval.
-
E.
subrange
chosen
Indicates that one value or interval lies entirely within the bounds of another value or interval.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a009273634c8190b5b9c87053b56760 |
completed | May 10, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_6a0092171230819096e4274dd97e0410 |
completed | May 10, 2026, 2:11 p.m. |
Created at: April 29, 2026, 8:27 p.m.