Triple
T37435469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wellfleet Town Meeting |
E930250
|
entity |
| Predicate | agendaDocument |
P177485
|
FINISHED |
| Object | warrant |
—
|
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: warrant | Statement: [Wellfleet Town Meeting, agendaDocument, warrant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agendaDocument Context triple: [Wellfleet Town Meeting, agendaDocument, warrant]
-
A.
agendaForm
chosen
Indicates that an entity serves as or takes the form of an agenda, typically specifying the structure or format of planned items or discussions.
-
B.
agendaItem
Indicates that something is an item or entry on a planned agenda or schedule of topics to be addressed.
-
C.
agendaSetBy
Indicates that the agenda for an event, meeting, or process is determined or established by a particular agent or entity.
-
D.
documentsActivity
Indicates that one entity records, describes, or provides evidence of an activity performed by another entity.
-
E.
officeAction
Indicates an official act or decision taken by an office or authority in response to a matter, request, or proceeding.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.