Triple
T526682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Controlled Substances Act |
E10933
|
entity |
| Predicate | schedule |
P15179
|
FINISHED |
| Object | Schedule I |
—
|
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: Schedule I | Statement: [Controlled Substances Act, schedule, Schedule I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schedule Context triple: [Controlled Substances Act, schedule, Schedule I]
-
A.
plan
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
B.
planner
Indicates that an entity is responsible for organizing, scheduling, or coordinating activities, tasks, or resources.
-
C.
agendaItem
Indicates that something is an item or entry on a planned agenda or schedule of topics to be addressed.
-
D.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
E.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
- F. None of above. chosen
Provenance (4 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d0d22081908aad915482d39e74 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0198ecc8190883849e5a8245963 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f0dcff1881909c18e8c599c150a1 |
completed | Feb. 28, 2026, 1:42 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.