Triple
T8245975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCW 90.58 |
E192848
|
entity |
| Predicate | requiresConsistencyWith |
P29598
|
FINISHED |
| Object | state shoreline management policies |
—
|
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: state shoreline management policies | Statement: [RCW 90.58, requiresConsistencyWith, state shoreline management policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresConsistencyWith Context triple: [RCW 90.58, requiresConsistencyWith, state shoreline management policies]
-
A.
requiresCompatibilityWith
Indicates that one entity can only function correctly or be used if it is compatible with another specified entity.
-
B.
requiresConcurrenceWith
Indicates that one action, decision, or condition must be agreed upon or approved by another specified party or entity before it can proceed or be valid.
-
C.
consistentWith
chosen
Indicates that one entity does not contradict and is compatible or in agreement with another entity, condition, or set of constraints.
-
D.
consistencyModel
Indicates that one entity adheres to, implements, or is governed by a particular consistency model in its behavior or operations.
-
E.
typicalConsistency
Indicates that one entity characteristically maintains a regular or expected level of consistency in relation to another entity or context.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb787414508190a08cf47d1545ce50 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.