Triple
T14770332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-119 |
E347112
|
entity |
| Predicate | notableForPhotography |
P23855
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [M-119, notableForPhotography, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableForPhotography Context triple: [M-119, notableForPhotography, yes]
-
A.
hasPhotographicSignificance
chosen
Indicates that something holds notable importance or relevance in the context of photography, such as for documentation, artistic value, or visual record.
-
B.
notablePhotographer
Indicates that the subject is a photographer who is recognized as notable or significant in some context.
-
C.
oftenPhotographedAt
Indicates that an entity is frequently the subject of photographs taken at a particular location or during a specific event.
-
D.
photographedByTourists
Indicates that the subject has been photographed by people visiting as tourists.
-
E.
notableFilmingLocation
Indicates that a place served as a significant or well-known location where a film or television production was shot.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec81334e08190a77d760e507d00ed |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.