Triple
T3938550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryans Road, Maryland |
E90973
|
entity |
| Predicate | censusDesignationYear |
P292
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Bryans Road, Maryland, censusDesignationYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: censusDesignationYear Context triple: [Bryans Road, Maryland, censusDesignationYear, 2010]
-
A.
basedOnCensusYear
Indicates that something (such as data, a decision, or a classification) is derived from or determined using information from a specific census year.
-
B.
populationCensusYear
chosen
Indicates the specific year in which an official population census was conducted or recorded for an entity.
-
C.
censusDesignatedPlace
Indicates that an entity is classified as a census-designated place, i.e., a populated area defined for statistical purposes by a census authority.
-
D.
heritageDesignationYear
Indicates the year in which something was formally granted a particular heritage designation or status.
-
E.
designYear
Indicates the year in which something was originally designed or conceived.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedcfd7d48190bbacee8b5b1b5070 |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.