Triple
T27028197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post-9/11 GI Bill |
E680846
|
entity |
| Predicate | appliesToServiceAfter |
P181213
|
FINISHED |
| Object | 2001-09-10 |
—
|
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: 2001-09-10 | Statement: [Post-9/11 GI Bill, appliesToServiceAfter, 2001-09-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToServiceAfter Context triple: [Post-9/11 GI Bill, appliesToServiceAfter, 2001-09-10]
-
A.
appliesToAfter
Indicates that one entity becomes relevant or applicable only after another specified event, condition, or time has occurred.
-
B.
appliesToServiceType
Indicates that something is relevant or applicable specifically to a particular type or category of service.
-
C.
isServedAfter
Indicates that one event, item, or course is provided or occurs later in sequence than another.
-
D.
afterService
Indicates that one event, action, or state occurs subsequent to the completion of a specified service.
-
E.
implementedAfter
Indicates that one implementation occurs or is introduced only after another specified implementation has taken place or been completed.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 27, 2026, 7:12 a.m.