Triple
T11040585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Battalion Grenadier Guards |
E261001
|
entity |
| Predicate | guardingResponsibility |
P636
|
FINISHED |
| Object | royal residences in London |
—
|
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: royal residences in London | Statement: [1st Battalion Grenadier Guards, guardingResponsibility, royal residences in London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardingResponsibility Context triple: [1st Battalion Grenadier Guards, guardingResponsibility, royal residences in London]
-
A.
securityResponsibilityModel
Indicates the framework or scheme that defines how security responsibilities are allocated and managed among involved parties.
-
B.
responsibleFor
chosen
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
C.
guardType
Indicates the specific kind or category of guarding role or protection associated with an entity.
-
D.
guardedAs
Indicates that one entity is protected, watched over, or kept secure in the role or capacity specified by another entity.
-
E.
protectionRole
Indicates that one entity serves a protective function or responsibility toward another entity or resource.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7980050948190ae7b187da5b776ca |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.