Triple
T25654991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baksho Rahashya |
E643207
|
entity |
| Predicate | hasCompanionOfDetective |
P180885
|
FINISHED |
| Object | Topshe |
—
|
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: Topshe | Statement: [Baksho Rahashya, hasCompanionOfDetective, Topshe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionOfDetective Context triple: [Baksho Rahashya, hasCompanionOfDetective, Topshe]
-
A.
companionOfDetective
chosen
Indicates a relationship where one entity serves as the detective’s close associate or partner, typically accompanying and assisting them in their investigative work.
-
B.
hasFictionalDetective
Indicates that one entity (typically a work or series) features or includes a fictional detective character as part of its content.
-
C.
hasClericalDetective
Indicates that an entity includes or is associated with a detective who is also a member of the clergy.
-
D.
featuresDetectiveDuo
Indicates that the subject involves or centers around a pair of detectives working together as a team.
-
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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 21, 2026, 6:32 p.m.