Triple
T3647356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turia River |
E77332
|
entity |
| Predicate | formerRiverbedUse |
P48489
|
FINISHED |
| Object | urban park |
—
|
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: urban park | Statement: [Turia River, formerRiverbedUse, urban park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerRiverbedUse Context triple: [Turia River, formerRiverbedUse, urban park]
-
A.
formerlyUsedBy
chosen
Indicates that an entity was used by another entity in the past but is no longer in use by that entity.
-
B.
usedRite
Indicates that an entity performed, followed, or applied a particular rite or ritual in some context.
-
C.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
-
D.
alsoUsedBy
Indicates that something is additionally utilized or employed by another entity, beyond any primary or previously mentioned user.
-
E.
formerProduct
Indicates that an entity was previously a product of another entity but is no longer in that role or status.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc38aa2388190bf1af926375e2433 |
completed | March 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.