Triple
T9624949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's South Africa Medal |
E232435
|
entity |
| Predicate | claspInscriptionType |
P16929
|
FINISHED |
| Object | battle names |
—
|
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: battle names | Statement: [Queen's South Africa Medal, claspInscriptionType, battle names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claspInscriptionType Context triple: [Queen's South Africa Medal, claspInscriptionType, battle names]
-
A.
claspIndicates
Indicates a relationship where one entity grasps, holds, or fastens onto another, typically in a secure or enclosing manner.
-
B.
claspPolicy
Indicates that an entity enforces or is governed by a specific CLASP (or similar) security or access control policy.
-
C.
methodOfInscription
Indicates the technique or process used to inscribe or engrave content onto a surface.
-
D.
inscriptionType
chosen
Indicates the specific kind or category of inscription associated with an entity (e.g., dedicatory, funerary, commemorative).
-
E.
inscribedUnder
Indicates that one entity is written, carved, or engraved beneath another entity, typically as a subordinate or accompanying inscription.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afb67c88190aa170716f0033752 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.