Triple
T13461967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trafalgar Falls |
E311393
|
entity |
| Predicate | photographyFeature |
P61635
|
FINISHED |
| Object | twin waterfall composition |
—
|
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: twin waterfall composition | Statement: [Trafalgar Falls, photographyFeature, twin waterfall composition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: photographyFeature Context triple: [Trafalgar Falls, photographyFeature, twin waterfall composition]
-
A.
photographyGenre
Indicates the specific genre or style of photography that characterizes a photographic work or activity.
-
B.
isPhotographicSubject
Indicates that an entity serves as the subject or main focus captured in a photograph taken by another entity.
-
C.
mediaFeature
Indicates a characteristic, capability, or attribute of a media item that distinguishes how it is presented, functions, or is experienced.
-
D.
usesPhotographyFrom
Indicates that one entity employs or incorporates photographic material originating from another entity.
-
E.
sceneFeature
chosen
Indicates a characteristic, element, or attribute that is present within or helps define a particular scene.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0d95fc81909d9f73d5315dc7b4 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:41 p.m.