Triple
T1331564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economic Opportunity Act of 1964 |
E28653
|
entity |
| Predicate | communityActionAuthorizedBy |
P27315
|
FINISHED |
| Object | Title II |
—
|
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: Title II | Statement: [Economic Opportunity Act of 1964, communityActionAuthorizedBy, Title II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityActionAuthorizedBy Context triple: [Economic Opportunity Act of 1964, communityActionAuthorizedBy, Title II]
-
A.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
B.
eligibleCommunity
Indicates that a community meets the required criteria or conditions to qualify for a specified program, benefit, or status.
-
C.
supportsCommunity
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
-
D.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
E.
associatedCommunity
Indicates a relationship where an entity is linked or connected to a particular community with which it is involved or identified.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c5f86c819098e98b046968954a |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0b1326081909aa6beec0cfe8d6c |
completed | March 1, 2026, 10:41 p.m. |
Created at: March 1, 2026, 7:55 p.m.