Triple
T37330823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuart Gharty |
E926738
|
entity |
| Predicate | hasPoliceRank |
P47215
|
FINISHED |
| Object | detective |
—
|
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 | Statement: [Stuart Gharty, hasPoliceRank, detective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliceRank Context triple: [Stuart Gharty, hasPoliceRank, detective]
-
A.
policeRank
chosen
Indicates that one entity holds a specific rank or position within a police organization relative to another entity.
-
B.
hasPoliceRole
Indicates that an entity holds or performs a specific role, duty, or function within a police or law enforcement context.
-
C.
hasPoliceAI
Indicates that an entity is equipped with, governed by, or utilizes an artificial intelligence system specifically for policing or law-enforcement functions.
-
D.
hasPolicePartner
Indicates that one entity has another entity as its partner in a police or law-enforcement context.
-
E.
policeRankStructure
Indicates the hierarchical ranking relationship that defines levels of authority and command within a police organization.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffb82be8148190a1c870d467a28c80 |
completed | May 9, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69ffb7bbd550819094052e9a0d0ae320 |
completed | May 9, 2026, 10:39 p.m. |
Created at: May 3, 2026, 4:16 p.m.