Triple
T34547143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polaroid photography |
E886955
|
entity |
| Predicate | sawRevivalDuring |
P27435
|
FINISHED |
| Object | 2010s |
—
|
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: 2010s | Statement: [Polaroid photography, sawRevivalDuring, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawRevivalDuring Context triple: [Polaroid photography, sawRevivalDuring, 2010s]
-
A.
sawRevivalIn
chosen
Indicates that an entity experienced a renewed interest, resurgence, or comeback during a specified time period or context.
-
B.
sawServiceAfterWar
Indicates that an entity served in a particular capacity or role after the end of a specified war.
-
C.
sawServiceDuring
Indicates that one entity experienced or utilized a service during the time period associated with another entity or event.
-
D.
sawActionDuring
Indicates that one entity observed an action or event occurring within a specific time period or during another event.
-
E.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72022cc348190a5a2e9aae263b638 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.