Triple
T17929191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyngenfjord |
E448281
|
entity |
| Predicate | isPhotographicLocation |
P49165
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lyngenfjord, isPhotographicLocation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPhotographicLocation Context triple: [Lyngenfjord, isPhotographicLocation, true]
-
A.
isPhotographicSubject
Indicates that an entity serves as the subject or main focus captured in a photograph taken by another entity.
-
B.
photographsTakenIn
Indicates that photographs were captured or taken within a specific location or place.
-
C.
hasPhotographicSignificance
Indicates that something holds notable importance or relevance in the context of photography, such as for documentation, artistic value, or visual record.
-
D.
oftenPhotographedAt
Indicates that an entity is frequently the subject of photographs taken at a particular location or during a specific event.
-
E.
hasPhotoSpot
chosen
Indicates that a location or entity includes or is associated with a designated place suitable for taking photographs.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a5511a408190973cf5fa1f286a26 |
completed | April 19, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:20 a.m.