Triple
T30325736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monroe County government (historical use) |
E771333
|
entity |
| Predicate | usedBuildingAsCourthouse |
P43987
|
FINISHED |
| Object | Old Monroe County Courthouse |
—
|
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: Old Monroe County Courthouse | Statement: [Monroe County government (historical use), usedBuildingAsCourthouse, Old Monroe County Courthouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBuildingAsCourthouse Context triple: [Monroe County government (historical use), usedBuildingAsCourthouse, Old Monroe County Courthouse]
-
A.
usedCourt
Indicates that an entity made use of or participated in legal proceedings within a particular court.
-
B.
hasCourthouse
Indicates that a location or jurisdiction possesses or contains a courthouse.
-
C.
courthouseHistoricUse
Indicates the historical function or role that a courthouse served in the past.
-
D.
usedAsCityHallFrom
Indicates that a building or location functioned as the official city hall of a municipality during a specified time period.
-
E.
buildingUsedBy
chosen
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 29, 2026, 7:52 p.m.