Triple
T4232543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Attorney of San Francisco |
E94612
|
entity |
| Predicate | mayHandle |
P31626
|
FINISHED |
| Object | civil enforcement actions |
—
|
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: civil enforcement actions | Statement: [City Attorney of San Francisco, mayHandle, civil enforcement actions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHandle Context triple: [City Attorney of San Francisco, mayHandle, civil enforcement actions]
-
A.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
B.
mayHead
Indicates that an entity is permitted or eligible to serve as the leader or head of another entity.
-
C.
canHandle
chosen
Indicates that an entity has the ability or capacity to manage, process, or deal with another entity or situation.
-
D.
mayFile
Indicates that an entity is permitted or authorized to submit or register a formal document or application.
-
E.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e642aac8190977dd101e27afcbb |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.