Triple
T9784180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Crook |
E237450
|
entity |
| Predicate | viewOnTopic |
P43390
|
FINISHED |
| Object | opposed corruption in the Indian Bureau |
—
|
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: opposed corruption in the Indian Bureau | Statement: [George Crook, viewOnTopic, opposed corruption in the Indian Bureau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnTopic Context triple: [George Crook, viewOnTopic, opposed corruption in the Indian Bureau]
-
A.
viewOnInterest
chosen
Indicates a perspective, opinion, or stance that one entity holds regarding a particular interest or topic.
-
B.
viewOnReason
Indicates that one entity holds or expresses a particular opinion, stance, or perspective about a specified reason or justification.
-
C.
viewOnHereafter
Indicates a subject’s beliefs, opinions, or perspective regarding the afterlife or what happens after death.
-
D.
viewOnKnowledge
Indicates the perspective, stance, or opinion one entity holds regarding another entity’s knowledge or understanding.
-
E.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
- 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1b7740c8190bfb4997eb683d78a |
completed | April 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.