Triple
T31726651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 55 Broadway |
E809734
|
entity |
| Predicate | laterTenant |
P43494
|
FINISHED |
| Object | London Transport Executive |
—
|
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: London Transport Executive | Statement: [55 Broadway, laterTenant, London Transport Executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTenant Context triple: [55 Broadway, laterTenant, London Transport Executive]
-
A.
laterOccupant
chosen
Indicates that one entity occupied or held a position in a place or role after another entity had previously done so.
-
B.
alsoTenant
Indicates that two or more entities share the status of being tenants, typically occupying the same property or rental arrangement.
-
C.
anchorTenant
Indicates that an entity serves as a primary or major tenant whose presence helps attract other tenants or users to a shared space or platform.
-
D.
mainTenant
Indicates that the subject is the primary tenant responsible for a property or rental agreement, as opposed to a subtenant or secondary occupant.
-
E.
alsoTenantFrom
Indicates that one entity is also a tenant originating from the same source, context, or provider as another 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: April 30, 2026, 11:20 p.m.