Triple
T29338438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIA Act, 2008 |
E743972
|
entity |
| Predicate | scheduleContains |
P14477
|
FINISHED |
| Object | list of scheduled offences |
—
|
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: list of scheduled offences | Statement: [NIA Act, 2008, scheduleContains, list of scheduled offences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduleContains Context triple: [NIA Act, 2008, scheduleContains, list of scheduled offences]
-
A.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
B.
containsSchedule
chosen
Indicates that one entity includes or holds a schedule associated with another entity or activity.
-
C.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
D.
scheduledBy
Indicates that an event, task, or appointment has been arranged or planned by a particular agent or entity.
-
E.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f669255db48190a9541c77cb9b5ede |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 1:32 p.m.