Triple
T20654449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Touch of Frost |
E507584
|
entity |
| Predicate | hasPoliceRankOfProtagonist |
P47215
|
FINISHED |
| Object | Detective Inspector |
—
|
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 Inspector | Statement: [A Touch of Frost, hasPoliceRankOfProtagonist, Detective Inspector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliceRankOfProtagonist Context triple: [A Touch of Frost, hasPoliceRankOfProtagonist, Detective Inspector]
-
A.
policeRank
chosen
Indicates that one entity holds a specific rank or position within a police organization relative to another entity.
-
B.
policeCharacter
Indicates that one entity serves as a police officer or law-enforcement figure in relation to another entity.
-
C.
hasPolicePartner
Indicates that one entity has another entity as its partner in a police or law-enforcement context.
-
D.
hasPoliceChief
Indicates that an entity has, is associated with, or is under the authority of a specific police chief.
-
E.
isHighestRankedUniformedOfficerIn
Indicates that one entity holds the top-ranking position among all uniformed officers within a specified organization or jurisdiction.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2ec90e881909250884483429acf |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.