Triple
T27028219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post-9/11 GI Bill |
E680846
|
entity |
| Predicate | housingAllowanceBasedOn |
P161786
|
FINISHED |
| Object | location of the school |
—
|
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: location of the school | Statement: [Post-9/11 GI Bill, housingAllowanceBasedOn, location of the school]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housingAllowanceBasedOn Context triple: [Post-9/11 GI Bill, housingAllowanceBasedOn, location of the school]
-
A.
housingAllowanceBasedOn
chosen
Indicates that a housing allowance is determined or calculated based on a specified factor, condition, or reference.
-
B.
allowsBoarderIncome
Indicates that an entity permits income to be earned or received from taking in boarders (people who pay to live in a room or part of a property).
-
C.
allowancesType
Indicates the specific category or kind of allowances associated with an entity or transaction.
-
D.
providedHousingFor
Indicates that one entity supplied or arranged housing or accommodation for another entity.
-
E.
housingPattern
Indicates the typical arrangement or distribution of housing units or residential structures within a given area or context.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62232f1048190be9e9467cd181055 |
completed | May 2, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 7:12 a.m.