Triple
T30140373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle city budget |
E766109
|
entity |
| Predicate | supportsPolicyGoals |
P39536
|
FINISHED |
| Object | public safety |
—
|
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: public safety | Statement: [Seattle city budget, supportsPolicyGoals, public safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPolicyGoals Context triple: [Seattle city budget, supportsPolicyGoals, public safety]
-
A.
supportsPolicyGoal
chosen
Indicates that one entity’s actions, positions, or characteristics help advance, uphold, or contribute to achieving a specified policy goal.
-
B.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
C.
supportsPolicyAgendaOf
Indicates that one entity actively endorses, promotes, or works to advance the policy agenda set by another entity.
-
D.
hasPolicyGoal
Indicates that an entity is associated with, or aims to achieve, a specific policy objective or target.
-
E.
supportsPolicyArea
Indicates that one entity endorses, advocates for, or is in favor of a particular policy area or domain of public policy.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:17 p.m.