Triple
T4711474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wem |
E104520
|
entity |
| Predicate | hasNotablePhotograph |
P12849
|
FINISHED |
| Object | Wem ghost photograph |
—
|
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: Wem ghost photograph | Statement: [Wem, hasNotablePhotograph, Wem ghost photograph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePhotograph Context triple: [Wem, hasNotablePhotograph, Wem ghost photograph]
-
A.
hasPhotograph
chosen
Indicates that one entity possesses, includes, or is associated with a photograph depicting or representing another entity.
-
B.
hasPhotographicRecordSince
Indicates that a photographic record of an entity has existed continuously since a specified point in time.
-
C.
hasPhotoSpot
Indicates that a location or entity includes or is associated with a designated place suitable for taking photographs.
-
D.
hasPhotographicSignificance
Indicates that something holds notable importance or relevance in the context of photography, such as for documentation, artistic value, or visual record.
-
E.
hasPhotoFeature
Indicates that an entity possesses a characteristic, capability, or option specifically related to photos or photography.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:17 p.m.