Triple
T26304473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1934 Surgeons Photograph |
E661643
|
entity |
| Predicate | takenInCountry |
P846
|
FINISHED |
| Object | Scotland |
—
|
NE NERFINISHED |
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: Scotland | Statement: [1934 Surgeons Photograph, takenInCountry, Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takenInCountry Context triple: [1934 Surgeons Photograph, takenInCountry, Scotland]
-
A.
meetsInCountry
Indicates that two or more entities have an in-person meeting that takes place within the specified country.
-
B.
consumedInCountry
Indicates that something (such as a product, resource, or item) is used up, eaten, or otherwise consumed within the borders of a specified country.
-
C.
endedInCountry
Indicates that an event, process, or entity’s existence or occurrence concluded within the boundaries of a specified country.
-
D.
reportedInCountry
Indicates that an event, case, or instance has been officially documented or reported within a specific country.
-
E.
hasCountry
chosen
Indicates that one entity possesses, is associated with, or is located within a specific country.
- 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_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_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 10:17 p.m.