Triple
T33861622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auburn Town Meeting |
E867938
|
entity |
| Predicate | agendaForm |
P177485
|
FINISHED |
| Object | warrant articles |
—
|
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 articles | Statement: [Auburn Town Meeting, agendaForm, warrant articles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agendaForm Context triple: [Auburn Town Meeting, agendaForm, warrant articles]
-
A.
agendaItem
Indicates that something is an item or entry on a planned agenda or schedule of topics to be addressed.
-
B.
agendaSetBy
Indicates that the agenda for an event, meeting, or process is determined or established by a particular agent or entity.
-
C.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
D.
calendarExample
Indicates a relationship where something serves as or provides an illustrative example within a calendar context (such as a sample date, event, or layout).
-
E.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
- F. None of above. chosen
Provenance (4 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6fcc44af48190b95fb9e12480a85f |
completed | May 3, 2026, 7:44 a.m. |
Created at: May 1, 2026, 1:47 a.m.