Triple
T28344933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constable Frank Gladstone |
E717923
|
entity |
| Predicate | policeForceInFiction |
P95623
|
FINISHED |
| Object | Gasforth police |
—
|
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: Gasforth police | Statement: [Constable Frank Gladstone, policeForceInFiction, Gasforth police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeForceInFiction Context triple: [Constable Frank Gladstone, policeForceInFiction, Gasforth police]
-
A.
policeCharacter
Indicates that one entity serves as a police officer or law-enforcement figure in relation to another entity.
-
B.
hasFictionalPoliceDepartment
chosen
Indicates that an entity is associated with or features a police department that exists only within a fictional or imaginary context.
-
C.
policeForceCharacteristic
Indicates that a specified characteristic, quality, or attribute is associated with a particular police force.
-
D.
rivalFictionalAgency
Indicates that one fictional agency stands in opposition or competition to another fictional agency.
-
E.
hasFictionalGovernmentAgency
Indicates that an entity includes, features, or is associated with a government agency that is fictional rather than real.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 12:42 a.m.