Triple
T7935021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereign’s Medal for Volunteers |
E184265
|
entity |
| Predicate | bilingualNameStatus |
P19196
|
FINISHED |
| Object | officially bilingual |
—
|
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: officially bilingual | Statement: [Sovereign’s Medal for Volunteers, bilingualNameStatus, officially bilingual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bilingualNameStatus Context triple: [Sovereign’s Medal for Volunteers, bilingualNameStatus, officially bilingual]
-
A.
bilingualName
Indicates that an entity has a name expressed in two different languages, linking the entity to its bilingual designation.
-
B.
isBilingual
Indicates that an entity is able to communicate fluently in two distinct languages.
-
C.
exonymStatus
Indicates the status or classification of a name used in one language to refer to a place, people, or entity known by a different name in its own language.
-
D.
nameStatus
chosen
Indicates the status or condition associated with an entity’s name, such as whether it is current, preferred, alternate, or deprecated.
-
E.
multilingualName
Indicates that an entity has one or more names expressed in multiple natural languages.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aec394081909a9569c02ac372af |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.