Triple
T27226855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lago de Valencia |
E682037
|
entity |
| Predicate | mainUseCurrent |
P104408
|
FINISHED |
| Object | limited recreation due to pollution |
—
|
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: limited recreation due to pollution | Statement: [Lago de Valencia, mainUseCurrent, limited recreation due to pollution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainUseCurrent Context triple: [Lago de Valencia, mainUseCurrent, limited recreation due to pollution]
-
A.
primaryCurrentUse
chosen
Indicates the main way something is currently being used or its principal present function.
-
B.
mainUseContinued
Indicates that the primary use or function of something persists or remains in effect over a subsequent period.
-
C.
mainCurrentAct
Indicates that an entity is currently performing or engaged in its primary or most important action or activity.
-
D.
currentUseOfRoute
Indicates that a particular route is presently being used for a specific purpose, activity, or traffic flow.
-
E.
exportUse
Indicates that something is used, intended, or suitable for export from one place or market to another.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 9:44 a.m.