Triple
T834263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orpheus Fountain |
E18034
|
entity |
| Predicate | waterFeature |
P20923
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Orpheus Fountain, waterFeature, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterFeature Context triple: [Orpheus Fountain, waterFeature, yes]
-
A.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
B.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
C.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
D.
waterColumnZone
Indicates the specific vertical region or layer within a body of water where an entity or process is located or occurs.
-
E.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
- F. None of above. chosen
Provenance (4 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb84fe081909b8f4b4202845860 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7c7df881909c539c3ab8ff0367 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:38 p.m.