Triple
T30233037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Finchley tube station |
E768682
|
entity |
| Predicate | rebuildFor |
P1510
|
FINISHED |
| Object | Northern Heights project |
—
|
NE NERFINISHED |
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: Northern Heights project | Statement: [East Finchley tube station, rebuildFor, Northern Heights project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildFor Context triple: [East Finchley tube station, rebuildFor, Northern Heights project]
-
A.
rebuiltFor
chosen
Indicates that one entity has been reconstructed, renovated, or modified specifically to serve the needs, purposes, or use of another entity.
-
B.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
-
C.
reconstructionFor
Indicates that one entity serves as a reconstruction, restoration, or rebuilt version of another entity.
-
D.
rebuiltUnder
Indicates that an entity was reconstructed or restored while being subject to the authority, control, or governance of another entity.
-
E.
rebuildType
Indicates the type or category of rebuilding or reconstruction process applied to an entity.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68048391c8190abe6580678f8a9ef |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:37 p.m.