Triple
T37867610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Río Darro |
E944517
|
entity |
| Predicate | parcialmenteCubiertoEn |
P16474
|
FINISHED |
| Object | centro de Granada |
—
|
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: centro de Granada | Statement: [Río Darro, parcialmenteCubiertoEn, centro de Granada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parcialmenteCubiertoEn Context triple: [Río Darro, parcialmenteCubiertoEn, centro de Granada]
-
A.
partlyCoveredBy
chosen
Indicates that one entity is covered or overlapped by another entity, but only to a partial extent rather than completely.
-
B.
partlyProtectedBy
Indicates that an entity is only partially safeguarded or covered by a specified protective measure, not fully protected.
-
C.
partiallyEnclosed
Indicates that one entity surrounds or covers another entity to some extent, but not completely.
-
D.
partiallyOn
Indicates that one entity rests or extends over another such that only a portion of its area, volume, or length is supported or in contact.
-
E.
partiallyClosed
Indicates that something is not fully closed, but also not fully open, occupying an intermediate state of closure.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.