Triple
T24735446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochester City Hall |
E618400
|
entity |
| Predicate | legislativeBodyMeetingPlace |
P8998
|
FINISHED |
| Object | Rochester City Council |
—
|
NE NERFINISHED |
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: Rochester City Council | Statement: [Rochester City Hall, legislativeBodyMeetingPlace, Rochester City Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeBodyMeetingPlace Context triple: [Rochester City Hall, legislativeBodyMeetingPlace, Rochester City Council]
-
A.
legislativeBodyLocated
Indicates that the physical location of a legislative body is at a specified place or jurisdiction.
-
B.
locationOfLegislature
Indicates the place where a legislature is situated or convenes.
-
C.
hasLegislatureBuilding
chosen
Indicates that one entity serves as the official legislature building or physical premises where the legislative body of another entity meets or operates.
-
D.
parliamentLocation
Indicates the place where a country's or region's parliament is situated or convenes.
-
E.
capitalOfMeetingPlace
Indicates that a location serves as the capital city where a particular meeting or set of meetings takes place.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:03 a.m.