Triple
T7095882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lack statue |
E165323
|
entity |
| Predicate | photographedAs |
P26354
|
FINISHED |
| Object | popular photo spot for visitors |
—
|
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 photo spot for visitors | Statement: [Lack statue, photographedAs, popular photo spot for visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: photographedAs Context triple: [Lack statue, photographedAs, popular photo spot for visitors]
-
A.
photographedFrom
Indicates that one entity serves as the vantage point or location from which another entity is photographed.
-
B.
hasPhotograph
Indicates that one entity possesses, includes, or is associated with a photograph depicting or representing another entity.
-
C.
imagedBy
Indicates that something is captured, recorded, or represented in an image created by a particular imaging device, method, or agent.
-
D.
imagedIn
Indicates that one entity appears within or is depicted in an image associated with another entity.
-
E.
photographedByTourists
chosen
Indicates that the subject has been photographed by people visiting as tourists.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e554d9f081909443be54eb501d25 |
completed | March 27, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.