Triple
T33567444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeton Township |
E859794
|
entity |
| Predicate | consolidationApprovedBy |
P807
|
FINISHED |
| Object | voters of Princeton Township |
—
|
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: voters of Princeton Township | Statement: [Princeton Township, consolidationApprovedBy, voters of Princeton Township]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consolidationApprovedBy Context triple: [Princeton Township, consolidationApprovedBy, voters of Princeton Township]
-
A.
consolidatedBy
Indicates that one entity has been merged, unified, or combined into a more cohesive whole by another entity.
-
B.
approvedBy
chosen
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
C.
consolidatedAs
Indicates that one entity has been combined, merged, or unified into another entity to form a single consolidated whole.
-
D.
consolidatedAfter
Indicates that one entity was formed or unified as a result of merging or combining multiple entities after a specified point in time.
-
E.
approvedAt
Indicates the date and time at which an entity received formal approval.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:40 a.m.