Triple
T23019216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Student Aid Report |
E573115
|
entity |
| Predicate | generatedAfter |
P3117
|
FINISHED |
| Object | FAFSA is processed |
—
|
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: FAFSA is processed | Statement: [Student Aid Report, generatedAfter, FAFSA is processed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generatedAfter Context triple: [Student Aid Report, generatedAfter, FAFSA is processed]
-
A.
createdAfterEvent
chosen
Indicates that the creation of one entity occurred after a specified event in time.
-
B.
releasedAfterSuccessOf
Indicates that one entity was released following, and likely in response to, the successful performance or reception of another entity.
-
C.
heldAfter
Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
-
D.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
E.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e777cc81908c0b0bfd9d5a717c |
completed | April 29, 2026, 4:07 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.