Triple
T20901761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raisina village |
E514685
|
entity |
| Predicate | clearedDuring |
P11808
|
FINISHED |
| Object | British rule in India |
—
|
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 rule in India | Statement: [Raisina village, clearedDuring, British rule in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clearedDuring Context triple: [Raisina village, clearedDuring, British rule in India]
-
A.
clearancePeriod
Indicates the span of time during which a particular authorization, permission, or clearance remains valid or in effect.
-
B.
destroyedDuring
chosen
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
C.
clearingSystem
Indicates that one entity functions as the financial clearing mechanism or infrastructure used to settle transactions for another entity.
-
D.
drainedDuring
Indicates that one entity had its resources, energy, or contents depleted in the course of another event or process.
-
E.
siteClearedBy
Indicates that a particular site has been cleared or prepared as a result of actions performed by a specified agent or 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8fc5d488190b62f51c35e768d38 |
completed | April 21, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.