Triple
T35857929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inspector-General |
E1036558
|
entity |
| Predicate | isOftenHeadOf |
P184209
|
FINISHED |
| Object | national police headquarters |
—
|
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: national police headquarters | Statement: [Inspector-General, isOftenHeadOf, national police headquarters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenHeadOf Context triple: [Inspector-General, isOftenHeadOf, national police headquarters]
-
A.
isHeadOf
Indicates that one entity holds the leading or principal authority position over another entity, such as an organization, group, or department.
-
B.
hasHeadOf
Indicates that one entity serves as the leader, chief, or person in charge of another entity (such as an organization, group, or department).
-
C.
areHeadedBy
Indicates that one entity serves as the leader or chief in charge of another entity.
-
D.
haveExecutiveHead
Indicates that one entity serves as the executive leader or chief authority (e.g., CEO, president, head of government) of another entity.
-
E.
isAtHeadOf
Indicates that an entity occupies the leading or foremost position in relation to another entity or ordered structure.
- F. None of above. chosen
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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7ac2210e481909279dade5328825c |
completed | May 3, 2026, 8:12 p.m. |
Created at: May 3, 2026, 4:06 p.m.