Triple
T11009416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Photograph |
E260207
|
entity |
| Predicate | notableLivePerformanceYear |
P89055
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Photograph, notableLivePerformanceYear, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLivePerformanceYear Context triple: [Photograph, notableLivePerformanceYear, 2002]
-
A.
notableLivePerformanceEvent
Indicates that an entity is a significant or widely recognized live performance event associated with another entity (such as an artist, work, or venue).
-
B.
notablePerformanceYear
chosen
Indicates the year in which an entity delivered a particularly significant or distinguished performance.
-
C.
notableLivePerformanceLocation
Indicates the venue or place where an entity is especially known for having given a significant or notable live performance.
-
D.
notableLiveRecording
Indicates that there exists a particularly significant or well-known live recording associated with the subject.
-
E.
notableConcert
Indicates that a concert event is recognized as particularly significant, memorable, or influential in some notable way.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79788d44c819084f35693ed96f422 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.