Triple
T26304500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1934 Surgeons Photograph |
E661643
|
entity |
| Predicate | laterConsensus |
P180119
|
FINISHED |
| Object | fabricated image |
—
|
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: fabricated image | Statement: [1934 Surgeons Photograph, laterConsensus, fabricated image]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterConsensus Context triple: [1934 Surgeons Photograph, laterConsensus, fabricated image]
-
A.
adoptedByConsensus
Indicates that a decision, action, or change was formally accepted through a consensus process among the relevant participants.
-
B.
laterConsentsTo
Indicates that one entity gives consent to another entity at a time subsequent to an earlier relevant event or point in the interaction.
-
C.
laterLeader
Indicates that one entity serves as a leader or holds a leadership role at a later time than another specified leader.
-
D.
supportsConsensus
Indicates that one entity endorses, upholds, or contributes to the achievement or maintenance of a shared agreement or collective decision among multiple parties.
-
E.
laterPolicy
Indicates that one policy occurs or becomes effective after another policy in time.
- F. None of above. chosen
Provenance (4 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: April 26, 2026, 10:18 p.m.