Triple
T10832427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swilcan Burn |
E255655
|
entity |
| Predicate | photographedWith |
P87094
|
FINISHED |
| Object | golfers crossing Swilcan Bridge |
—
|
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: golfers crossing Swilcan Bridge | Statement: [Swilcan Burn, photographedWith, golfers crossing Swilcan Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: photographedWith Context triple: [Swilcan Burn, photographedWith, golfers crossing Swilcan Bridge]
-
A.
isPhotographedWith
chosen
Indicates that two or more entities appear together in the same photograph or are captured jointly in an image.
-
B.
usesPhotographyFrom
Indicates that one entity employs or incorporates photographic material originating from another entity.
-
C.
hasPhotographBy
Indicates that an entity is depicted in or associated with a photograph that was created or taken by a specified photographer.
-
D.
hasPhotograph
Indicates that one entity possesses, includes, or is associated with a photograph depicting or representing another entity.
-
E.
imagedBy
Indicates that something is captured, recorded, or represented in an image created by a particular imaging device, method, or agent.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7442323948190afd9488815f7908b |
completed | April 9, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.