Triple
T16366276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bab Semmarine |
E397443
|
entity |
| Predicate | hasPhotographicSubjectType |
P116192
|
FINISHED |
| Object | architecture |
—
|
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: architecture | Statement: [Bab Semmarine, hasPhotographicSubjectType, architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhotographicSubjectType Context triple: [Bab Semmarine, hasPhotographicSubjectType, architecture]
-
A.
isPhotographicSubject
Indicates that an entity serves as the subject or main focus captured in a photograph taken by another entity.
-
B.
hasPhotographicSpecialty
chosen
Indicates that an entity possesses a specific area of expertise or focus within the field of photography.
-
C.
hasPhotogenicFeature
Indicates that an entity possesses a visual characteristic or attribute that is especially attractive or appealing when photographed.
-
D.
hasPhotographicIcon
Indicates that an entity is associated with or represented by a photographic image or icon.
-
E.
hasPhotographicConvention
Indicates that there is an established photographic style, rule, or convention governing how the related entities are visually represented in 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff3c915c81909e1757fc31921876 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.