Triple
T16514610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian princes |
E401148
|
entity |
| Predicate | wereSubjectOf |
P35270
|
FINISHED |
| Object | British imperial policy |
—
|
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: British imperial policy | Statement: [Indian princes, wereSubjectOf, British imperial policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereSubjectOf Context triple: [Indian princes, wereSubjectOf, British imperial policy]
-
A.
hasBeenSubjectOf
chosen
Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
-
B.
mayBeSubjectOf
Indicates that an entity has the potential or possibility to serve as the subject in a given relation, event, or statement.
-
C.
hasBeenInvolvedIn
Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
-
D.
notableWorkSubject
Indicates that a work is notably associated with a particular subject, such as a person, topic, or entity, as its primary focus or theme.
-
E.
notableStorySubject
Indicates that the subject is a prominent or central topic, character, or element within a particular story or narrative.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7a5ff88190984e2f2bc2fd17cc |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.