Triple
T35145118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone Hall |
E1014804
|
entity |
| Predicate | NRHPListingCounty |
P182331
|
FINISHED |
| Object | Baltimore County, Maryland |
—
|
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: Baltimore County, Maryland | Statement: [Stone Hall, NRHPListingCounty, Baltimore County, Maryland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NRHPListingCounty Context triple: [Stone Hall, NRHPListingCounty, Baltimore County, Maryland]
-
A.
NRHPListingLocation
Indicates that a location is the place where a specific property or site is listed on the National Register of Historic Places.
-
B.
NRHPListingCity
Indicates that a property listed on the National Register of Historic Places is located within a specified city.
-
C.
NRHPListingName
Indicates that a place or property has a specific official name under its listing in the National Register of Historic Places (NRHP).
-
D.
NRHPListingNearby
Indicates that one entity is located close to another entity that is listed on the National Register of Historic Places (NRHP).
-
E.
NRHPListingDate
Indicates the date on which something was officially listed in the National Register of Historic Places.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c337cec8190bfdab225a3cc96db |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 3, 2026, 4:02 p.m.