Triple
T6910866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centers for Independent Living programs |
E159926
|
entity |
| Predicate | oftenCollaboratesWith |
P398
|
FINISHED |
| Object | government agencies |
—
|
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: government agencies | Statement: [Centers for Independent Living programs, oftenCollaboratesWith, government agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCollaboratesWith Context triple: [Centers for Independent Living programs, oftenCollaboratesWith, government agencies]
-
A.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
B.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
C.
worksWith
chosen
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
D.
establishedInCollaborationWith
Indicates that something was created, founded, or set up jointly through cooperative effort between two or more parties.
-
E.
organizedInCollaborationWith
Indicates that an event, project, or activity was organized jointly in cooperation with another party or parties.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9c135b48190b332aedf1d52bdb7 |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.