Triple
T105114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reading Terminal Market |
E2121
|
entity |
| Predicate | cityDesignation |
P921
|
FINISHED |
| Object | historic market |
—
|
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: historic market | Statement: [Reading Terminal Market, cityDesignation, historic market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityDesignation Context triple: [Reading Terminal Market, cityDesignation, historic market]
-
A.
heritageDesignation
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
-
B.
UNESCOWorldHeritageDesignationYear
Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
-
C.
hasNatureDesignation
Indicates that something has been formally assigned a specific conservation, protection, or natural-area status or designation.
-
D.
UNPlazaDesignation
Indicates that a location has been officially designated as a United Nations Plaza or equivalent UN-recognized plaza area.
-
E.
hasHeritageDesignation
chosen
Indicates that an entity has been formally assigned a specific heritage or cultural protection status by an authoritative body.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563be81c81908ccc5ed44edd6b8e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.