Triple
T24871139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterloo Bridge (1931 film) |
E622428
|
entity |
| Predicate | locationInTitle |
P148434
|
FINISHED |
| Object | Waterloo Bridge |
—
|
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: Waterloo Bridge | Statement: [Waterloo Bridge (1931 film), locationInTitle, Waterloo Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInTitle Context triple: [Waterloo Bridge (1931 film), locationInTitle, Waterloo Bridge]
-
A.
associatedTitleLocation
chosen
Indicates a relationship where a title is linked to a specific location with which it is contextually or formally connected.
-
B.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
-
C.
timeLocatedIn
Indicates that an event, state, or entity occurs, exists, or is valid within a specified time or temporal interval.
-
D.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
locationPresented
Indicates that a specific location is presented or shown to an entity (such as a user or system) within a given context.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 5:23 a.m.