Triple
T28164411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green–Duwamish River watershed |
E714984
|
entity |
| Predicate | WRIANumber |
P8195
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Green–Duwamish River watershed, WRIANumber, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WRIANumber Context triple: [Green–Duwamish River watershed, WRIANumber, 9]
-
A.
OJNumber
Indicates that an entity is assigned a specific official journal or case identification number used for tracking or reference.
-
B.
number
chosen
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
C.
wardNumber
Indicates the specific ward identifier or number associated with an entity, typically within an institution like a hospital or electoral district.
-
D.
DKNumber
Indicates a numerical identifier or value associated with an entity within the DK (domain-specific) system.
-
E.
BDNumber
Indicates that an entity is associated with a specific BD (Business Development or similar domain-specific) identification number used to uniquely reference it.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f641ee03788190aa54b66d4919896f |
completed | May 2, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:08 p.m.