Triple
T37803232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jawahar Navodaya Vidyalayas |
E942435
|
entity |
| Predicate | selectionTestName |
P18903
|
FINISHED |
| Object | Jawahar Navodaya Vidyalaya Selection Test |
—
|
NE NERFINISHED |
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: Jawahar Navodaya Vidyalaya Selection Test | Statement: [Jawahar Navodaya Vidyalayas, selectionTestName, Jawahar Navodaya Vidyalaya Selection Test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionTestName Context triple: [Jawahar Navodaya Vidyalayas, selectionTestName, Jawahar Navodaya Vidyalaya Selection Test]
-
A.
testName
chosen
Indicates that an entity is identified or labeled by a specific test name.
-
B.
theoryTested
Indicates that a theory has been subjected to evaluation or experimentation to assess its validity or accuracy.
-
C.
testedAs
Indicates that one entity has been evaluated, examined, or subjected to a test in the role or capacity of another specified entity or condition.
-
D.
testType
Indicates the specific category or kind of test associated with an entity or event.
-
E.
containsTest
Indicates that one entity includes or encompasses another entity as a test or testing component.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.