Triple
T11057802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Empire Medal |
E261423
|
entity |
| Predicate | continuedInUse |
P27206
|
FINISHED |
| Object | some Commonwealth countries after 1993 |
—
|
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: some Commonwealth countries after 1993 | Statement: [British Empire Medal, continuedInUse, some Commonwealth countries after 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedInUse Context triple: [British Empire Medal, continuedInUse, some Commonwealth countries after 1993]
-
A.
continuedInServiceOn
Indicates that an entity remained active, operational, or in use beyond a specified point in time or event.
-
B.
stillUsedBy
chosen
Indicates that something continues to be used or relied upon by another entity at the present time.
-
C.
stillMaintained
Indicates that the subject continues to be actively maintained or supported over time.
-
D.
mainUseContinued
Indicates that the primary use or function of something persists or remains in effect over a subsequent period.
-
E.
continuedThrough
Indicates that an event, state, or process persisted without interruption across or beyond a specified point, period, or boundary.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a2efa48190b290f43dfe836501 |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.