Triple
T22076683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waman Rao v. Union of India |
E545539
|
entity |
| Predicate | temporalCutoffDate |
P140
|
FINISHED |
| Object | 24 April 1973 |
—
|
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: 24 April 1973 | Statement: [Waman Rao v. Union of India, temporalCutoffDate, 24 April 1973]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalCutoffDate Context triple: [Waman Rao v. Union of India, temporalCutoffDate, 24 April 1973]
-
A.
cutOffDateYear
Indicates the calendar year that serves as the cutoff point beyond which something no longer applies, is valid, or is considered.
-
B.
hasTemporalEnd
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
C.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
D.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
E.
cappingDate
Indicates the date on which a limit, cap, or maximum condition is set, becomes effective, or is reached for the related entities or values.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b2bf60819082d38e671f160b0f |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.