Triple
T34698063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nine Streets |
E891084
|
entity |
| Predicate | typicalBuildingPeriod |
P103862
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Nine Streets, typicalBuildingPeriod, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBuildingPeriod Context triple: [Nine Streets, typicalBuildingPeriod, 17th century]
-
A.
associatedBuildingDate
Indicates the date on which a particular building is formally linked or related to another entity or record.
-
B.
buildingUsedSince
Indicates that a particular building has been in use starting from a specified point in time.
-
C.
historicBuildingDate
Indicates the date on which a building was originally constructed or formally recognized as historic.
-
D.
timePeriodOfArchitecture
chosen
Indicates the historical time period or era during which a particular architectural work, style, or feature was created or predominantly used.
-
E.
hasBuildingPeriod
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:05 a.m.