Triple
T27155665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Order of Victoria and Albert |
E682511
|
entity |
| Predicate | locationOfInsigniaCollection |
P4762
|
FINISHED |
| Object | Royal Collection, United Kingdom |
—
|
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: Royal Collection, United Kingdom | Statement: [Royal Order of Victoria and Albert, locationOfInsigniaCollection, Royal Collection, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfInsigniaCollection Context triple: [Royal Order of Victoria and Albert, locationOfInsigniaCollection, Royal Collection, United Kingdom]
-
A.
insigniaLocation
Indicates the physical position or placement of an insignia on or relative to an entity.
-
B.
hasOfficialInsigniaLocation
chosen
Indicates the specific place where an entity’s official insignia is physically located or displayed.
-
C.
hasInsigniaComponent
Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
-
D.
locationOfInsigniaTheft
Indicates the place where the theft of an insignia occurred.
-
E.
insigniaName
Indicates the specific name or designation assigned to an insignia associated with an entity.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: April 27, 2026, 9:16 a.m.