Triple
T10529437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detective Chief Inspector |
E248396
|
entity |
| Predicate | rankLevelBelow |
P11456
|
FINISHED |
| Object | Detective Superintendent |
—
|
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: Detective Superintendent | Statement: [Detective Chief Inspector, rankLevelBelow, Detective Superintendent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankLevelBelow Context triple: [Detective Chief Inspector, rankLevelBelow, Detective Superintendent]
-
A.
membershipLevelBelow
Indicates that one entity’s membership level is ranked lower or less privileged than another entity’s membership level.
-
B.
lowerRank
chosen
Indicates that one entity holds an inferior or subordinate rank, status, or position relative to another entity.
-
C.
rankRestriction
Indicates a constraint or limit placed on the rank or hierarchical level that an entity may hold within a given system or structure.
-
D.
isEntryLevelRankFor
Indicates that a rank represents the lowest or starting level within a particular role, position, or hierarchy.
-
E.
rankRange
Indicates that an entity’s rank falls within a specified minimum and maximum range.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509f7d8ac8190b90c1a7f77b23545 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:30 p.m.