Triple
T37789235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSRS |
E942035
|
entity |
| Predicate | coordinationWithSocialSecurity |
P146333
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [CSRS, coordinationWithSocialSecurity, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinationWithSocialSecurity Context triple: [CSRS, coordinationWithSocialSecurity, limited]
-
A.
benefitCoordination
Indicates that one entity gains an advantage or positive outcome through the organized cooperation or alignment of actions with another entity.
-
B.
coordinationWithBenefits
chosen
Indicates a relationship where entities coordinate their actions or plans in a way that yields mutual or shared benefits.
-
C.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
D.
coordinateRoleIn
Indicates a relationship where one entity organizes, aligns, or manages the roles or responsibilities of another entity within a shared activity, structure, or context.
-
E.
coordina
Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group toward a common goal.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:19 p.m.