Triple
T10575840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Household Division Brigade of Guards |
E249608
|
entity |
| Predicate | guardResponsibility |
P636
|
FINISHED |
| Object | royal palaces 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 palaces in London | Statement: [Household Division Brigade of Guards, guardResponsibility, royal palaces in London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardResponsibility Context triple: [Household Division Brigade of Guards, guardResponsibility, royal palaces in London]
-
A.
guardType
Indicates the specific kind or category of guarding role or protection associated with an entity.
-
B.
guardedAs
Indicates that one entity is protected, watched over, or kept secure in the role or capacity specified by another entity.
-
C.
securityResponsibilityModel
Indicates the framework or scheme that defines how security responsibilities are allocated and managed among involved parties.
-
D.
guardMounting
Indicates the action of assigning or taking up a position for guard duty, typically as part of a scheduled security or watch rotation.
-
E.
responsibleFor
chosen
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5274b100c8190b477ef4cb745c269 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:38 p.m.