Triple
T2810160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Reserve Bank of Richmond |
E54147
|
entity |
| Predicate | districtCode |
P43726
|
FINISHED |
| Object | E |
—
|
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: E | Statement: [Federal Reserve Bank of Richmond, districtCode, E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: districtCode Context triple: [Federal Reserve Bank of Richmond, districtCode, E]
-
A.
districtBasedOn
Indicates that one district is defined, derived, or established based on the boundaries, characteristics, or structure of another entity or area.
-
B.
district
Indicates that one entity is an administrative or electoral district that geographically contains or governs another entity.
-
C.
communityDistrictNumber
Indicates the specific community district identifier associated with an entity or location.
-
D.
areaCode
Indicates that a location, phone number, or region is associated with a specific telephone area code.
-
E.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde335b38819090c70d5e2ca14d79 |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde0f4c648190b9812e64f30c39da |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 9:59 p.m.