Triple
T22540407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Richmond |
E557272
|
entity |
| Predicate | isBoroughCoterminousWithCounty |
P148589
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [County of Richmond, isBoroughCoterminousWithCounty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBoroughCoterminousWithCounty Context triple: [County of Richmond, isBoroughCoterminousWithCounty, true]
-
A.
isCentralBoroughOf
Indicates that a borough serves as the primary or central administrative or geographic district of a specified city or region.
-
B.
hasBoroughEquivalent
Indicates that one administrative area corresponds functionally or hierarchically to a borough in another jurisdiction or classification system.
-
C.
isBoroughSeatOf
Indicates that a place serves as the administrative center or seat of government for a specific borough.
-
D.
hasBoroughCode
Indicates that an entity is associated with a specific borough identified by a particular code.
-
E.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f3196fc819098deffb0c7932ccc |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:51 p.m.