Triple
T26304471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1934 Surgeons Photograph |
E661643
|
entity |
| Predicate | takenOn |
P160229
|
FINISHED |
| Object | 1934 |
—
|
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: 1934 | Statement: [1934 Surgeons Photograph, takenOn, 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takenOn Context triple: [1934 Surgeons Photograph, takenOn, 1934]
-
A.
appointedOn
Indicates the specific date or time at which an entity is formally assigned or designated to a role, position, or responsibility.
-
B.
conductedOn
Indicates that an action, process, or event was carried out with respect to, or took place on, a specified subject, object, or medium.
-
C.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
D.
achievedOn
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
-
E.
takenInBy
Indicates that one entity is absorbed, ingested, or otherwise brought inside and contained by another entity.
- 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_69f60ee22a908190a62640e48c2e7659 |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 10:17 p.m.