Triple
T7541715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Fountain |
E178291
|
entity |
| Predicate | waterDisplayType |
P7148
|
FINISHED |
| Object | synchronized fountain show |
—
|
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: synchronized fountain show | Statement: [International Fountain, waterDisplayType, synchronized fountain show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterDisplayType Context triple: [International Fountain, waterDisplayType, synchronized fountain show]
-
A.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
B.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
C.
waterServiceType
Indicates the specific kind or category of water service provided or associated with an entity.
-
D.
displayType
chosen
Indicates the manner or format in which something is presented, shown, or rendered.
-
E.
waterAllocatedTo
Indicates that a specified amount or portion of water has been designated or assigned for use by a particular entity, location, or purpose.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8750f80819088ddfb7a5580b5df |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.