Triple
T32155366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventure of Black Peter |
E821272
|
entity |
| Predicate | policeInspector |
P31758
|
FINISHED |
| Object | Inspector Stanley Hopkins |
—
|
NE NERFINISHED |
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: Inspector Stanley Hopkins | Statement: [The Adventure of Black Peter, policeInspector, Inspector Stanley Hopkins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeInspector Context triple: [The Adventure of Black Peter, policeInspector, Inspector Stanley Hopkins]
-
A.
policeCharacter
chosen
Indicates that one entity serves as a police officer or law-enforcement figure in relation to another entity.
-
B.
policeBureau
Indicates that an entity functions as or is associated with a police bureau or police department.
-
C.
policeDescription
Indicates that an entity serves as or provides a descriptive account or characterization of a police-related entity, role, action, or situation.
-
D.
chiefLawOfficer
Indicates that one entity serves as the highest-ranking legal authority or primary legal officer for another entity.
-
E.
detectiveType
Indicates that one entity is classified as a particular type or category of detective in relation to 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 12:32 a.m.