Triple
T12343512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concubine Lane |
E294288
|
entity |
| Predicate | photographyAppeal |
P23855
|
FINISHED |
| Object | popular Instagram spot |
—
|
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: popular Instagram spot | Statement: [Concubine Lane, photographyAppeal, popular Instagram spot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: photographyAppeal Context triple: [Concubine Lane, photographyAppeal, popular Instagram spot]
-
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.
usesPhotographyFrom
Indicates that one entity employs or incorporates photographic material originating from another entity.
-
D.
hasPhotographicSignificance
chosen
Indicates that something holds notable importance or relevance in the context of photography, such as for documentation, artistic value, or visual record.
-
E.
allowsPhotography
Indicates that one entity permits another entity to take photographs in a particular context or location.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f78a970819086beec3e4da8c49e |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.