Triple
T20885721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angat–Ipo–La Mesa water system |
E514273
|
entity |
| Predicate | suppliesUse |
P22211
|
FINISHED |
| Object | domestic water use |
—
|
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: domestic water use | Statement: [Angat–Ipo–La Mesa water system, suppliesUse, domestic water use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppliesUse Context triple: [Angat–Ipo–La Mesa water system, suppliesUse, domestic water use]
-
A.
suppliesIndustry
Indicates that one entity provides goods, services, or resources to support the operations or needs of an industry or industrial sector.
-
B.
suppliesTo
Indicates that one entity provides or delivers goods, services, or resources to another entity.
-
C.
usedSupplyMethod
Indicates that an entity employed a particular method or process to supply or deliver something.
-
D.
materialProvidedFor
chosen
Indicates that one entity supplies or makes available a material for use, processing, or incorporation by another entity or purpose.
-
E.
workUsedFor
Indicates that a particular work (such as a document, artwork, or dataset) is employed or utilized for a specific purpose, task, or function.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67c9d1c81908031eb77c124f119 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.