Triple
T24132231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Guard (Bahrain) |
E597984
|
entity |
| Predicate | isEliteWithin |
P37488
|
FINISHED |
| Object | Bahrain Defence Force |
E27432
|
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: Bahrain Defence Force | Statement: [Royal Guard (Bahrain), isEliteWithin, Bahrain Defence Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEliteWithin Context triple: [Royal Guard (Bahrain), isEliteWithin, Bahrain Defence Force]
-
A.
isEliteUnit
chosen
Indicates that the unit belongs to a specially trained, highly capable subgroup distinguished from regular units.
-
B.
eliteStatusProgram
Indicates a relationship where an entity is enrolled in or associated with a special high-tier or privileged status program.
-
C.
isPremium
Indicates that an entity has premium status, typically granting enhanced or paid-tier features or privileges compared to a standard version.
-
D.
isPrestigeLevel
Indicates that an entity possesses a particular status or rank associated with prestige or high standing.
-
E.
eliteTierSystem
Indicates a relationship where entities are organized or classified into higher, privileged levels within a tiered ranking or status system.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df78b6f08190809fc154110fa201 |
completed | April 29, 2026, 10:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fe33dc44481908e6053b4f9d6e988 |
completed | May 22, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:25 p.m.