Triple
T25385573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsham Street |
E631513
|
entity |
| Predicate | hasGovernmentDepartment |
P8853
|
FINISHED |
| Object | Home Office |
—
|
NE NERFINISHED |
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: Home Office | Statement: [Marsham Street, hasGovernmentDepartment, Home Office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentDepartment Context triple: [Marsham Street, hasGovernmentDepartment, Home Office]
-
A.
governmentBranch
Indicates that one entity functions as an official division or branch within the structure of a government.
-
B.
hasGovernmentInstitution
chosen
Indicates that a given entity possesses, hosts, or is served by a formal governmental body or institution.
-
C.
isPartOfGovernment
Indicates that an entity belongs to, is included within, or functions as a component of a governmental body or system.
-
D.
governmentBranchAlongside
Indicates that one branch of government exists or operates alongside another as a parallel or coequal component within the same governmental system.
-
E.
hasGovernmentBody
Indicates that one entity serves as the official governing or administrative body responsible for overseeing or managing another entity.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5656795248190a732c8596a0e740d |
completed | May 2, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:47 p.m.