Triple
T24311185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Barnstable, Massachusetts |
E612676
|
entity |
| Predicate | hasCountyCourt |
P7595
|
FINISHED |
| Object | Barnstable 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: Barnstable County Courthouse | Statement: [Town of Barnstable, Massachusetts, hasCountyCourt, Barnstable County Courthouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyCourt Context triple: [Town of Barnstable, Massachusetts, hasCountyCourt, Barnstable County Courthouse]
-
A.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
B.
hasStateCourt
Indicates that a given jurisdiction or region possesses an official court that operates at the state level.
-
C.
hasCountyJudge
Indicates that a specified jurisdiction or administrative area is served or overseen by a particular county judge.
-
D.
hasCourthouse
chosen
Indicates that a location or jurisdiction possesses or contains a courthouse.
-
E.
hasCountyCouncil
Indicates that an entity is administratively governed or overseen by a specific county council.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922a6afc8190b02cc2d185d15a45 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:37 a.m.