Triple
T23657003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Addicks |
E584330
|
entity |
| Predicate | associatedWithCityBorough |
P300
|
FINISHED |
| Object | Royal Borough of Greenwich |
—
|
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: Royal Borough of Greenwich | Statement: [The Addicks, associatedWithCityBorough, Royal Borough of Greenwich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCityBorough Context triple: [The Addicks, associatedWithCityBorough, Royal Borough of Greenwich]
-
A.
hasBoroughCouncil
Indicates that an administrative area is governed or overseen by a specific borough council.
-
B.
containsCityOrBorough
Indicates that a geographic or administrative area includes, within its boundaries, a specific city or borough.
-
C.
hasBorough
chosen
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
D.
hasLondonBorough
Indicates that an entity includes, contains, or is associated with a specific London borough as one of its administrative subdivisions.
-
E.
associatedWithCounty
Indicates that an entity has a relationship or linkage to a specific county, such as jurisdiction, location, or administrative association.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35c257c81909f7004c0a35be4e3 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.