Triple
T6205246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Director, Intelligence Bureau |
E138728
|
entity |
| Predicate | rankComparableTo |
P18223
|
FINISHED |
| Object | Director General of Police |
—
|
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: Director General of Police | Statement: [Director, Intelligence Bureau, rankComparableTo, Director General of Police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankComparableTo Context triple: [Director, Intelligence Bureau, rankComparableTo, Director General of Police]
-
A.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
B.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
-
C.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
D.
hasComparableRank
chosen
Indicates that two entities hold positions or levels that are equivalent or similar in rank within a given hierarchy or system.
-
E.
rankIndicated
Indicates that one entity specifies, denotes, or reveals the hierarchical rank or level of 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626d96ec8190816c00c44668177d |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.