Triple
T23817910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netra |
E589144
|
entity |
| Predicate | hasOriginProgram |
P17523
|
FINISHED |
| Object | Indian AEW&C programme |
—
|
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: Indian AEW&C programme | Statement: [Netra, hasOriginProgram, Indian AEW&C programme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginProgram Context triple: [Netra, hasOriginProgram, Indian AEW&C programme]
-
A.
originProgram
chosen
Indicates the program, initiative, or source project from which an entity, item, or record originally comes.
-
B.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
D.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
E.
hasParentProgram
Indicates that a given program is hierarchically contained within or derived from another, higher-level program that serves as its parent.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7ac0c688190a627b9b42c7587d5 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:58 p.m.