Triple
T27226853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lago de Valencia |
E682037
|
entity |
| Predicate | mainUseHistorical |
P2715
|
FINISHED |
| Object | recreation |
—
|
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: recreation | Statement: [Lago de Valencia, mainUseHistorical, recreation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainUseHistorical Context triple: [Lago de Valencia, mainUseHistorical, recreation]
-
A.
historicalBase
Indicates that one entity serves as the original or foundational source, model, or precedent upon which the other entity is historically based.
-
B.
hasPrimaryUseHistoric
Indicates that something is primarily used for historic or heritage-related purposes.
-
C.
usesHistoricalAnalysis
Indicates that an entity employs historical analysis as a method or approach to understand, evaluate, or explain something.
-
D.
towerUseHistorical
Indicates that a tower has been used for historical purposes or holds significance due to its historical use.
-
E.
historicalFunction
chosen
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
- 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_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 9:44 a.m.