Triple
T27452027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hickman Bridge |
E692469
|
entity |
| Predicate | isPhotogenicAt |
P49165
|
FINISHED |
| Object | late afternoon |
—
|
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: late afternoon | Statement: [Hickman Bridge, isPhotogenicAt, late afternoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPhotogenicAt Context triple: [Hickman Bridge, isPhotogenicAt, late afternoon]
-
A.
hasPhotogenicFeature
Indicates that an entity possesses a visual characteristic or attribute that is especially attractive or appealing when photographed.
-
B.
isPhotographicSubject
Indicates that an entity serves as the subject or main focus captured in a photograph taken by another entity.
-
C.
hasPhotoSpot
chosen
Indicates that a location or entity includes or is associated with a designated place suitable for taking photographs.
-
D.
missPhotogenicWinner
Indicates that an entity is the winner of a Miss Photogenic title or award in a given context.
-
E.
hasPhotographicSignificance
Indicates that something holds notable importance or relevance in the context of photography, such as for documentation, artistic value, or visual record.
- 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62dc69f1481908717ae77e60d9658 |
completed | May 2, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:47 p.m.