Triple
T5915920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 87-293 |
E131579
|
entity |
| Predicate | programTypeAuthorized |
P2192
|
FINISHED |
| Object | volunteer service abroad |
—
|
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: volunteer service abroad | Statement: [Public Law 87-293, programTypeAuthorized, volunteer service abroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programTypeAuthorized Context triple: [Public Law 87-293, programTypeAuthorized, volunteer service abroad]
-
A.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
-
B.
programType
chosen
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
C.
administersProgramType
Indicates that an entity is responsible for managing or overseeing a specific type or category of program.
-
D.
establishedForProgram
Indicates that something has been created or set up specifically to support, serve, or be used by a particular program.
-
E.
establishedProgram
Indicates that an entity has created and put into operation a formal program that is now in an active, ongoing state.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.