Triple
T7902874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardroom Estate |
E183496
|
entity |
| Predicate | streetPatternChangedBy |
P79680
|
FINISHED |
| Object | New Islington masterplan |
—
|
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: New Islington masterplan | Statement: [Cardroom Estate, streetPatternChangedBy, New Islington masterplan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetPatternChangedBy Context triple: [Cardroom Estate, streetPatternChangedBy, New Islington masterplan]
-
A.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
B.
streetFunction
Indicates the functional role or primary use of a street within a transportation or urban context (e.g., residential, arterial, commercial access).
-
C.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
D.
streetOrientedAlong
Indicates that a street is aligned or runs in the same general direction as a specified reference feature or axis.
-
E.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other entity.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a41b0fc81909890f2e4f432a5cf |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:02 p.m.