Triple
T37624172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snohomish County Charter |
E936155
|
entity |
| Predicate | notSupersede |
P5512
|
FINISHED |
| Object | Washington State Constitution |
—
|
NE NERFINISHED |
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: Washington State Constitution | Statement: [Snohomish County Charter, notSupersede, Washington State Constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notSupersede Context triple: [Snohomish County Charter, notSupersede, Washington State Constitution]
-
A.
notSubordinateTo
Indicates that one entity is not in a lower-ranking, subordinate, or reporting position to another entity within a hierarchy or organizational structure.
-
B.
notWithin
Indicates that one entity is located outside the spatial or conceptual bounds of another entity.
-
C.
doesNotAbolish
chosen
Indicates that one entity, action, or law does not eliminate, revoke, or put an end to another.
-
D.
notUsedOver
Indicates that one entity has not been used, applied, or utilized for a duration exceeding a specified time period relative to another entity or reference point.
-
E.
notAfter
Indicates that one event or entity does not occur later than (i.e., is earlier than or at the same time as) another in an ordering or timeline.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.