Triple
T36602628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumpole’s chambers |
E902958
|
entity |
| Predicate | hasNotableFictionalMember |
P141846
|
FINISHED |
| Object | Horace Rumpole |
E48880
|
NE 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: Horace Rumpole | Statement: [Rumpole’s chambers, hasNotableFictionalMember, Horace Rumpole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFictionalMember Context triple: [Rumpole’s chambers, hasNotableFictionalMember, Horace Rumpole]
-
A.
hasFictionalMember
chosen
Indicates that a group, organization, or collection includes at least one member that is fictional rather than real.
-
B.
hasFictionalStaffMember
Indicates that an entity includes or employs a staff member who is a fictional character.
-
C.
hasNotableFictionalBearer
Indicates that an entity is associated with at least one well-known fictional character that bears its name or designation.
-
D.
hasFictionalLeadCharacter
Indicates that a creative work features a particular fictional character as its main or leading protagonist.
-
E.
hasFictionalSpokesperson
Indicates that an entity is represented or promoted by a spokesperson who is a fictional or imaginary character.
- F. None of above.
Provenance (4 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a095744c481908287d32f80c3a1f2 |
completed | June 23, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.