Triple
T31746421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King's South Africa Medal |
E810280
|
entity |
| Predicate | locationOfDesignApproval |
P45143
|
FINISHED |
| Object | London |
E1817
|
NE 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: London | Statement: [King's South Africa Medal, locationOfDesignApproval, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfDesignApproval Context triple: [King's South Africa Medal, locationOfDesignApproval, London]
-
A.
locationOfOriginalApproval
Indicates the place or jurisdiction where the initial authorization, consent, or formal approval for something was first granted.
-
B.
designLocation
chosen
Indicates the place or setting where something is conceived, planned, or designed.
-
C.
commissioningLocation
Indicates the place where an entity (such as a work, project, or item) is formally commissioned or initiated.
-
D.
commissionedStructureLocation
Indicates the place where a commissioned structure is situated or intended to be built.
-
E.
designedForLocation
Indicates that something has been created or configured specifically to be used in, or suited to, a particular location.
- F. None of above.
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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01bb9c33cc8190a95ba124d97edf99 |
completed | May 11, 2026, 11:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b945a49a48190ab9bde63c52dc01c |
completed | June 12, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_6a01bb6772148190a243d1141ad0a237 |
completed | May 11, 2026, 11:20 a.m. |
Created at: April 30, 2026, 11:26 p.m.