Triple
T419550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation A |
E8069
|
entity |
| Predicate | permitsTestingTheWaters |
P14694
|
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: [Regulation A, permitsTestingTheWaters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permitsTestingTheWaters Context triple: [Regulation A, permitsTestingTheWaters, yes]
-
A.
drinkingWaterStandard
Indicates that something meets an established quality or safety standard for drinking water.
-
B.
recreationAccess
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another entity.
-
C.
hasStructureOnWatercourse
Indicates that a structure is physically located on, over, or directly associated with a specific watercourse.
-
D.
appliesToWaterBody
Indicates that something (such as a rule, condition, property, or effect) is relevant or applicable specifically to a particular water body.
-
E.
includesWatersOff
Indicates that a geographic or administrative area’s scope explicitly extends to and covers the adjacent offshore waters.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd3b948819097d96c73d0a0f699 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2eeb8545c8190a2b8517e7ed5b92e |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.