Triple
T29348537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commissioner Julius Enderby |
E744237
|
entity |
| Predicate | governingConcern |
P150490
|
FINISHED |
| Object | public order in the City |
—
|
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: public order in the City | Statement: [Commissioner Julius Enderby, governingConcern, public order in the City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingConcern Context triple: [Commissioner Julius Enderby, governingConcern, public order in the City]
-
A.
governingSee
Indicates that a governing authority observes, oversees, or monitors another entity or situation.
-
B.
sectorGoverned
Indicates that a particular sector or domain is under the authority, control, or regulatory oversight of a specified governing entity.
-
C.
governmentConcerned
chosen
Indicates that a government has a particular interest in, worry about, or focus on a specific issue, entity, or situation.
-
D.
councilConcernedWith
Indicates that a council has responsibility for, oversight of, or active interest in a particular issue, subject, or matter.
-
E.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: April 28, 2026, 2:04 p.m.