Triple
T36500817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterloo Bridge |
E899320
|
entity |
| Predicate | officiallyInaugurated |
P24169
|
FINISHED |
| Object | 1945-12-10 |
—
|
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: 1945-12-10 | Statement: [Waterloo Bridge, officiallyInaugurated, 1945-12-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officiallyInaugurated Context triple: [Waterloo Bridge, officiallyInaugurated, 1945-12-10]
-
A.
officialInauguration
Indicates the formal ceremony or event at which someone is officially installed into an office, position, or role.
-
B.
inauguratedWith
chosen
Indicates that an event, position, or institution was formally initiated or opened through a specific ceremony, action, or accompanying element.
-
C.
inaugurated
Indicates that a person is formally introduced or installed into an official position, office, or role through a ceremonial event.
-
D.
inauguratedFor
Indicates that a formal ceremony or event was held to officially begin or dedicate something specifically for a particular entity, role, or purpose.
-
E.
inauguratedAfter
Indicates that one entity’s formal inauguration occurred later in time than another entity’s inauguration.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
Created at: May 3, 2026, 4:10 p.m.