Triple
T7121165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress of India |
E165952
|
entity |
| Predicate | reasonForNotUsedBy |
P37640
|
FINISHED |
| Object | title lapsed with Indian independence |
—
|
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: title lapsed with Indian independence | Statement: [Empress of India, reasonForNotUsedBy, title lapsed with Indian independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNotUsedBy Context triple: [Empress of India, reasonForNotUsedBy, title lapsed with Indian independence]
-
A.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
B.
reasonForNonOperation
Indicates the specific cause or explanation for why an entity, system, or process is not currently operating or functioning.
-
C.
discouragedUsageReason
chosen
Indicates the reason why a particular usage, action, or practice is considered discouraged.
-
D.
reasonForNonParticipation
Indicates the explanation or cause for why an entity did not take part in a specified activity or event.
-
E.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61e67788190959fbd7fa6c929d3 |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:44 p.m.