Triple
T26464177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiltern |
E665712
|
entity |
| Predicate | hasHistoricStreetscape |
P181112
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chiltern, hasHistoricStreetscape, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricStreetscape Context triple: [Chiltern, hasHistoricStreetscape, true]
-
A.
hasHistoricStreet
Indicates that an entity is associated with or located on a street that has recognized historical significance.
-
B.
isHistoricStreet
Indicates that a street has recognized historical significance or heritage status.
-
C.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
-
D.
isHistoricDistrict
Indicates that an area has been officially recognized or designated as a historic district due to its historical, cultural, or architectural significance.
-
E.
isHistoricQuadrangleOf
Indicates that one entity is a historically significant quadrangle (a four-sided courtyard or enclosed area) that belongs to, or is a defining part of, another entity such as a campus, complex, or site.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 27, 2026, 12:14 a.m.