Triple
T5787033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shard London Bridge |
E128291
|
entity |
| Predicate | hasResidences |
P65840
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shard London Bridge, hasResidences, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidences Context triple: [Shard London Bridge, hasResidences, yes]
-
A.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
B.
hasResidenceFeature
Indicates that a residence possesses or is characterized by a specific feature or attribute.
-
C.
servedAsResidenceOf
Indicates that something functioned as the home or dwelling place of a particular person or group.
-
D.
formerResidenceOf
Indicates that a location was once the place where a person or entity lived or was based, but is no longer their current residence.
-
E.
hasExclusiveResidence
Indicates that an entity resides in exactly one specific place and has no other concurrent residences.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a1c29d48190af36cc855bb491dd |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c024861bc88190a17782c1982fbb3e |
completed | March 22, 2026, 5:19 p.m. |
Created at: March 22, 2026, 3:51 p.m.