Triple
T2203106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Market historic district |
E50535
|
entity |
| Predicate | eraOfMostBuildings |
P22153
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Old Market historic district, eraOfMostBuildings, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfMostBuildings Context triple: [Old Market historic district, eraOfMostBuildings, late 19th century]
-
A.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
B.
oldestStandingStructureIn
Indicates that one entity is the oldest still-existing structure located within the specified place or region.
-
C.
earliestMajorConstruction
Indicates the earliest significant construction event associated with an entity, such as the first major building or development work completed for it.
-
D.
eraOfMostBurials
Indicates the historical time period during which the greatest number of burials occurred for a given site or context.
-
E.
placeBuilt
Indicates that a structure or facility was constructed at a specific location.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa33f0881908403604eafb73ecf |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.