Triple
T5787030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shard London Bridge |
E128291
|
entity |
| Predicate | hotelLocation |
P64875
|
FINISHED |
| Object | floors 34–52 |
—
|
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: floors 34–52 | Statement: [Shard London Bridge, hotelLocation, floors 34–52]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotelLocation Context triple: [Shard London Bridge, hotelLocation, floors 34–52]
-
A.
reservationLocatedIn
Indicates that a reservation (such as a booking or held resource) is situated within or associated with a specific location or place.
-
B.
reservationLocatedAlong
Indicates that a reservation is situated along, adjacent to, or following the course or extent of a specified linear feature such as a road, river, or boundary.
-
C.
locationProperty
chosen
Indicates that one entity specifies or characterizes a locational attribute or spatial property of another entity.
-
D.
locationDetail
Indicates a more specific or refined description of a location associated with an entity or event.
-
E.
locationDescription
Indicates a textual description that specifies or characterizes the location of 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_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. |
Created at: March 22, 2026, 3:51 p.m.