Triple
T3784697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman bridge of Tavira |
E85501
|
entity |
| Predicate | isPhotographedAs |
P37258
|
FINISHED |
| Object | scenic viewpoint over Gilão River |
—
|
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: scenic viewpoint over Gilão River | Statement: [Roman bridge of Tavira, isPhotographedAs, scenic viewpoint over Gilão River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPhotographedAs Context triple: [Roman bridge of Tavira, isPhotographedAs, scenic viewpoint over Gilão River]
-
A.
hasPhotograph
Indicates that one entity possesses, includes, or is associated with a photograph depicting or representing another entity.
-
B.
imagedBy
Indicates that something is captured, recorded, or represented in an image created by a particular imaging device, method, or agent.
-
C.
imagedIn
chosen
Indicates that one entity appears within or is depicted in an image associated with another entity.
-
D.
isPhotographicSubject
Indicates that an entity serves as the subject or main focus captured in a photograph taken by another entity.
-
E.
evokesImageOf
Indicates that one entity triggers or brings to mind a mental image or visual representation of another 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d3c92c819081d9d5c45ef37a5d |
completed | March 9, 2026, 3:14 p.m. |
Created at: March 9, 2026, 3:13 p.m.